Thanks for the pointer, Winston.
This will certainly cut down on config time for new jobs.
Denis
On 09/25/2012 12:10 PM, Winston Prakash wrote:
Since Eclipse Hudson instance is upgraded to 2.2.1, I thought it may
be worth to mention about a helpful feature we introduced in Hudson
2.2.0. This
Since Eclipse Hudson instance is upgraded to 2.2.1, I thought it may be
worth to mention about a helpful feature we introduced in Hudson 2.2.0.
This is a useful feature especially if you have several jobs with
similar configurations and maintaining them is a painful process.
In Hudson 2.2.0, w
Thanks Igor,
I raised https://bugs.eclipse.org/bugs/show_bug.cgi?id=390334 against
community/servers to ask for the inclusion of this file on the build
server. Please complete it if I am missing some information :).
Laurent
On 25/09/2012 15:25, Igor Fedorenko wrote:
This is correct, Tycho c
If you use bugs.eclipse.org a lot, then you could be interested in this
Greasemonkey script:
http://www.eclipse.org/jdt/ui/scripts/jdtbugzilla.user.js
It fixes quite a few Bugzilla UI bloopers and adds handy functionality.
See http://www.eclipse.org/jdt/ui/dev.php#scripts for a list of features.
Thanks for trying Matt, but
https://hudson.eclipse.org/hudson/view/Virgo/job/virgo.artifact-repository.snapshot/752/
still shows a flashing blue ball and some small amount of progress on the
progress bar, so I don't think it's quite dead yet. I tried a force refresh of
the browser *and* another
This is correct, Tycho considers toolchain.xml only if it is explicitly
told to. Projects that do not specify useJDK=BREE will not be affected.
--
Regards,
Igor
On 12-09-25 9:22 AM, Laurent Goubet wrote:
This is what I feared. We are back to one of the questions I sneaked
into the first mail th
This is what I feared. We are back to one of the questions I sneaked
into the first mail then :
If anyone has some input as to whether this "toolchains.xml" should be
provided for all jobs that would like to use it.
Currently, the Eclipse hudson instance launches all builds (at least,
those
We can copy the job configs between the master and sandbox, but I'd
prefer to have projects 'volunteer'(as the J&EGit folks have done) to
try out the sandbox changes instead of my randomly picking projects and
possibly hosing their builds(you're not writing directly into your
downloads area via
I've killed the job and it seems to be dead.
-Matt.
Dear Web Master
I would be grateful if you could kill the following job, or recycle
enough of Hudson to kill it:
https://hudson.eclipse.org/hudson/view/Virgo/job/virgo.artifact-repository.snapshot/752/
We've tried multiple times and it
You need to create toolchain.xml in ~/.m2 of the user that runs hudson
jobs, which likely means webmaster needs to do this.
--
Regards,
Igor
On 12-09-25 7:46 AM, Laurent Goubet wrote:
Igor,
The problem (I think) is that /my/ '~' directory is not what hudson will
search when I run the hudson jo
Igor,
The problem (I think) is that /my/ '~' directory is not what hudson will
search when I run the hudson job. Isn't the build run with the
'hudsonBuild' user? I've just tried to copy/paste the toolchains.xml
file attached to the bug you've linked to in my own ~/.m2 directory ...
but this r
Okay, forget this last mention about my tests failing because of the
surefire plugin... this was a mistake from my side. All other questions
remain though :).
Laurent
On 25/09/2012 13:05, Laurent Goubet wrote:
Hi all,
One of our plugins cannot be compiled against java 1.6 and has to be
comp
toolchain.xml must be available on slave in ~/.m2 directory. You can
find sample toolchain.xml and libraries that correspond to restricted
execution environments attached to bug 386649 [1]. Beware that there is
currently an outstanding issue with IBM JDKs tracked as bug 389856 [2]
[1] https://bug
Hi all,
One of our plugins cannot be compiled against java 1.6 and has to be
compiled with the javac of jdk 1.5. In short, one of the jdk classes has
changed the signature of one of its methods' generics between the two
versions (see version 1.5 [1] and version 1.6 [2]). AFAIK, the
incompatib
Dear Web Master
I would be grateful if you could kill the following job, or recycle enough of
Hudson to kill it:
https://hudson.eclipse.org/hudson/view/Virgo/job/virgo.artifact-repository.snapshot/752/
We've tried multiple times and it won't die.
Thanks.
Regards,
Glyn
___
Hello Matt,
is it somehow possible to copy some of the regular
hudson jobs to the sandbox instance, to have a test drive?
Or maybe even auto copy once a week or so.
Best regards,
Dennis Hübner
Xtext Commiter / Build Engineer
Mobile: +49 (0) 151 / 17 39 67 07
Telefon: +49 (0) 431 / 990 268 70
Fa
16 matches
Mail list logo
