M5 spin status :: no aggregate or JBDS installers available yet; many bot and non-UI test failures, plus one inter-build compilation failure
by Nick Boldt
Since turning on the stable branch jobs, here's what's borked...
https://issues.jboss.org/browse/JBIDE-10349
Still trying to get a clean stable_branch aggregate build (and then JBT
builds too) - last time the aggregate failed due to missing Central,
OTDT, and OpenShift (hadn't spun clean yet).
---
Details:
- hibernate : test failure in org.hibernate.eclipse.console.test
- jbpm : test failure in org.jboss.tools.jbpm.convert.test
- jsf : test failure in org.jboss.tools.jsf.vpe.jsf.test
- maven : 15 bot test failures (same failures in trunk) ... should these
just be turned off and only run locally / manually?
- struts : COMPILE FAILED - upstream bits missing? "The import
org.jboss.tools.jst.web.validation cannot be resolved."
---
There are also a few jobs for which the latest build failed, but at
least we have one good build since branching. This suggests we're having
some stability issues w/ a few Jenkins slaves, but at least we're
getting clean spins when the server is quiet(er).
= archives : aborted build? [Dec 4 ok]
= birt : failed to find usage bits (poor timing between builds) [Dec 4 ok]
= seam : no more locks failure [Dec 4 ok]
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
7 months, 2 weeks
Plan to remove installation-tests from the jbosstools-base repo
by Mickael Istria
Hi all,
As tracked in https://issues.jboss.org/browse/JBIDE-12905 , we are
trying to move installation tests out of jbosstools-base/tests since it
is something that comes on top of JBT/JBDS, and which is not part of the
base. We decided it would make its own git repo, since it's not exactly
integration tests neither, and also because we can anticipate the fact
that some other "Stacks" (SOA, Fuse...) would like to use it to test
their update-sites.
So the repo is here:
https://github.com/jbosstools/jbosstools-install-grinder . Most stuff
was updated to work well with this change.
We're just waiting for some QA jobs will be adapted. Pavol is leading
this stuff for QA side. When he migrates to the new repo/job/URLs and
everything is working well, we'll remove this stuff from jbosstools-base.
The plan is to do it ASAP, but we are not in a hurry for that. So if
Pavol has some more important tasks to do, we'll wait after GA.
Does anyone have any objection, concern or question on this topic?
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
13 years, 9 months
INFO: jbosstools-build-sites push forced
by Max Rydahl Andersen
Hi,
We had some non-public/non-reviewed code from JBDS go into jbosstools-build-sites repo a few hours ago by accident.
Since it was discovered quickly I went and push forced the latest clean version of jbosstools-build-sites.
Thus if you have jbosstools-build-sites checked out or updated within the last 2 hrs you will need to refetch and rebase your custom branches.
If not then this should not affect you :)
Ping me if any problems.
Thanks,
/max
13 years, 10 months
Could not resolve target platform
by Andrej Podhradsky
Hi folks,
I'm not able to resolve the new TP org.jboss.tools.target-platforms.jbosstools:unified:target:unified:4.2.0.c-SNAPSHOT
See my log in the attachment.
It seems that it isn't in the nexus repository, right?
--
Andrej Podhradsky
Quality Assurance Associate
JBoss SOA Platform
IRC: apodhrad at #jbossqa #jbosssoa #jbosssoaqa #devstudio-qa #brno
13 years, 10 months
new repo on github: jbosstools-install-grinder
by Max Rydahl Andersen
Hey,
FYI, I've just created jbosstools-install-grinder which Mickael Istria shortly will start filling up.
This repo will be the new place for the p2 and jboss central swtbot based tests Micakel and Pavol have
currently buried inside jbosstools-base where they had some funky circular dependencies and heavy build impacts.
By moving it out these can be more easily run by others and reused to for example testing more complex stacks and more combinations.
Mickael will send out the PR to cut out the old installscripts repo.
/max
13 years, 10 months
On the topic of useful PR title/descriptions and git commit messages
by Max Rydahl Andersen
Hey,
I'm seeing a tendency to just put the JIRA number + possible merge info in the topic of the pullrequest and git commit messages are long lines of text instead of properly formatted.
This makes it rather hard to look at the list of PR and git history and figure out what they are about plus they duplicate the merge info Github already knows about.
You might not be aware that git actually uses some rules/conventions on the git messages to make things like git log be readable and informative, git rebase and squash etc. can use the titles better and finally github uses the same conventions for their pull requests.
Thus if you treat the github pullrequest similar to how a good git commit comment is done (you can even copy/paste them if there is a 1-to-1 match) then we should be good.
Thus the basic conventions are:
1 line for title, max 50 characters and don't end with a '.'
Two new lines
paragraph of text, max 72 characters wide containing the necessary info/details.
And that 1 line title for our workflow is best started with the jira ID.
Thus a good minimal commit message would look like this:
JBIDE-1234 - hibernate tools 4 classloading is broken.
Because of changes in Hibernate 4 classloader we can no longer
do XYZ. Thus I've made it do ZXY instead.
For a PR you can either just copy verbatim the above or maybe add some refs/details:
JBIDE-1234 - hibernate tools 4 classloading is broken.
This should be applied not only to master but also branch jbosstools-4.0.x
With this github dashboard and git log messages becomes much more informative.
Links with more background/tips with respect to commits/messages/workflows:
http://who-t.blogspot.cz/2009/12/on-commit-messages.html
http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
/max
13 years, 10 months
