Re: [cross-project-issues-dev] Trigger simrel.mars.runaggregator.VALIDATE when pushing directly to repo

2015-05-29 Thread Alexander Nyßen 
You are right, I am actually able to manually trigger the VALIDATE build (after 
having logged in). I probably looked into it now without having logged in and 
had a look into a different build (when having been logged in) before. Sorry 
for that.

However, the Git changes do not seem to be recognized properly. I raised 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=468866 
 to keep track of it.

Cheers
Alexander

> Am 29.05.2015 um 21:51 schrieb David M Williams :
> 
> You should be able to trigger a build. You have to log-in, of course. But if 
> you can commit to org.eclipse.simrel.build repo, you should be able to build. 
> (that job, not others) ... at least I set it up that way, with that group 
> having the 'build" checkbox "on". And it is set up to check for Git changes, 
> once every 15 minutes. And, the Git polling log looks normal. (below).
> 
> If anyone sees anything other than the above intended behavior, please open a 
> cross-project bug and I'll investigate.
> 
> = = = = = =
> 
> Started on May 29, 2015 3:46:01 PM
> Using strategy: Default
> [poll] Last Build : #317
> [poll] Last Built Revision: Revision da42bbcecff928795ace19e0a1d76524355798bc 
> (origin1/master)
> Fetching changes from the remote Git repositories
> Fetching upstream changes from 
> git://git.eclipse.org/gitroot/simrel/org.eclipse.simrel.build
> Seen branch in repository origin/Juno_maintenance
> Seen branch in repository origin/Juno_maintenance_A
> Seen branch in repository origin/KeplerPostRC4_branch
> Seen branch in repository origin/Kepler_maintenance
> Seen branch in repository origin/Luna_maintenance
> Seen branch in repository origin/Luna_maintenance_limited
> Seen branch in repository origin/david_williams/testMultiSets
> Seen branch in repository origin/david_williams/testnewbuild
> Seen branch in repository origin/master
> Fetching changes from the remote Git repositories
> Fetching upstream changes from 
> git://git.eclipse.org/gitroot/simrel/org.eclipse.simrel.tools
> Seen branch in repository origin1/Kepler_maintenance
> Seen branch in repository origin1/david_williams/testTests
> Seen branch in repository origin1/david_williams/testnewbuild
> Seen branch in repository origin1/master
> Fetching changes from the remote Git repositories
> Fetching upstream changes from 
> git://git.eclipse.org/gitroot/simrel/org.eclipse.simrel.tests
> Seen branch in repository origin2/Kepler_maintenance
> Seen branch in repository origin2/david_williams/testTests
> Seen branch in repository origin2/david_williams/testnewbuild
> Seen branch in repository origin2/dhubner/junit
> Seen branch in repository origin2/master
> Done. Took 1 sec
> No changes
> 
> 
> 
> 
> From:Alexander Nyßen 
> To:Cross project issues ,
> Date:05/29/2015 03:26 PM
> Subject:[cross-project-issues-dev] Trigger
> simrel.mars.runaggregator.VALIDATE when pushing directly to repo
> Sent by:cross-project-issues-dev-boun...@eclipse.org
> 
> 
> 
> Is there a way to trigger simrel.mars.runaggregator.VALIDATE after having 
> pushed directly to the repo (i.e. not via Gerrit)?
> 
> To me it seems the build is neither configured to watch Git for changes nor 
> does it allow committers to manually trigger a build. If pushing to the repo 
> directly is an option, there should IMHO also be a way to trigger a build 
> afterwards.
> 
> Cheers
> Alexander
> --
> Dr. Alexander Nyßen
> Dipl.-Inform.
> Principal Engineer
> 
> Telefon: +49 (0) 231 / 98 60-202
> Telefax: +49 (0) 231 / 98 60-211
> Mobil: +49 (0) 151 /  17396743
> 
> http://www.itemis.de 
> alexander.nys...@itemis.de 
> 
> itemis AG
> Am Brambusch 15-24
> 44536 Lünen
> 
> Rechtlicher Hinweis:
> 
> Amtsgericht Dortmund, HRB 20621
> 
> Vorstand: Jens Wagener (Vors.), Wolfgang Neuhaus, Dr. Georg Pietrek, Jens 
> Trompeter, Sebastian Neus
> 
> Aufsichtsrat: Prof. Dr. Burkhard Igel (Vors.), Michael Neuhaus, Jennifer 
> Fiorentino
> 
> 
> [attachment "signature.asc" deleted by David M Williams/Raleigh/IBM] 
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe from 
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev 
> 
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe from 
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

--
Dr. Alexander Nyßen
Dipl.-Inform.
Principal Engineer

Telefon: +49 (0) 231 / 98 60-202
Telefax: +49 (0) 231 / 98 60-211
Mobil: +49 (0) 151 /  17396743

http://www.itemis.de
alexander.nys...@itemis.de

item

Re: [cross-project-issues-dev] Trigger simrel.mars.runaggregator.VALIDATE when pushing directly to repo

2015-05-29 Thread David M Williams 
You should be able to trigger a build. You have to log-in, of course. But 
if you can commit to org.eclipse.simrel.build repo, you should be able to 
build. (that job, not others) ... at least I set it up that way, with that 
group having the 'build" checkbox "on". And it is set up to check for Git 
changes, once every 15 minutes. And, the Git polling log looks normal. 
(below). 

If anyone sees anything other than the above intended behavior, please 
open a cross-project bug and I'll investigate. 

= = = = = =

Started on May 29, 2015 3:46:01 PM
Using strategy: Default
[poll] Last Build : #317
[poll] Last Built Revision: Revision 
da42bbcecff928795ace19e0a1d76524355798bc (origin1/master)
Fetching changes from the remote Git repositories
Fetching upstream changes from 
git://git.eclipse.org/gitroot/simrel/org.eclipse.simrel.build
Seen branch in repository origin/Juno_maintenance
Seen branch in repository origin/Juno_maintenance_A
Seen branch in repository origin/KeplerPostRC4_branch
Seen branch in repository origin/Kepler_maintenance
Seen branch in repository origin/Luna_maintenance
Seen branch in repository origin/Luna_maintenance_limited
Seen branch in repository origin/david_williams/testMultiSets
Seen branch in repository origin/david_williams/testnewbuild
Seen branch in repository origin/master
Fetching changes from the remote Git repositories
Fetching upstream changes from 
git://git.eclipse.org/gitroot/simrel/org.eclipse.simrel.tools
Seen branch in repository origin1/Kepler_maintenance
Seen branch in repository origin1/david_williams/testTests
Seen branch in repository origin1/david_williams/testnewbuild
Seen branch in repository origin1/master
Fetching changes from the remote Git repositories
Fetching upstream changes from 
git://git.eclipse.org/gitroot/simrel/org.eclipse.simrel.tests
Seen branch in repository origin2/Kepler_maintenance
Seen branch in repository origin2/david_williams/testTests
Seen branch in repository origin2/david_williams/testnewbuild
Seen branch in repository origin2/dhubner/junit
Seen branch in repository origin2/master
Done. Took 1 sec
No changes




From:   Alexander Nyßen 
To: Cross project issues , 
Date:   05/29/2015 03:26 PM
Subject:[cross-project-issues-dev] Trigger 
simrel.mars.runaggregator.VALIDATE when pushing directly to repo
Sent by:cross-project-issues-dev-boun...@eclipse.org



Is there a way to trigger simrel.mars.runaggregator.VALIDATE after having 
pushed directly to the repo (i.e. not via Gerrit)? 

To me it seems the build is neither configured to watch Git for changes 
nor does it allow committers to manually trigger a build. If pushing to 
the repo directly is an option, there should IMHO also be a way to trigger 
a build afterwards.

Cheers
Alexander
--
Dr. Alexander Nyßen
Dipl.-Inform.
Principal Engineer

Telefon: +49 (0) 231 / 98 60-202
Telefax: +49 (0) 231 / 98 60-211
Mobil: +49 (0) 151 /  17396743

http://www.itemis.de 
alexander.nys...@itemis.de 

itemis AG
Am Brambusch 15-24
44536 Lünen

Rechtlicher Hinweis:

Amtsgericht Dortmund, HRB 20621

Vorstand: Jens Wagener (Vors.), Wolfgang Neuhaus, Dr. Georg Pietrek, Jens 
Trompeter, Sebastian Neus

Aufsichtsrat: Prof. Dr. Burkhard Igel (Vors.), Michael Neuhaus, Jennifer 
Fiorentino


[attachment "signature.asc" deleted by David M Williams/Raleigh/IBM] 
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe 
from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Trigger simrel.mars.runaggregator.VALIDATE when pushing directly to repo

2015-05-29 Thread Alexander Nyßen 
Is there a way to trigger simrel.mars.runaggregator.VALIDATE after having 
pushed directly to the repo (i.e. not via Gerrit)?

To me it seems the build is neither configured to watch Git for changes nor 
does it allow committers to manually trigger a build. If pushing to the repo 
directly is an option, there should IMHO also be a way to trigger a build 
afterwards.

Cheers
Alexander
--
Dr. Alexander Nyßen
Dipl.-Inform.
Principal Engineer

Telefon: +49 (0) 231 / 98 60-202
Telefax: +49 (0) 231 / 98 60-211
Mobil: +49 (0) 151 /  17396743

http://www.itemis.de
alexander.nys...@itemis.de

itemis AG
Am Brambusch 15-24
44536 Lünen

Rechtlicher Hinweis:

Amtsgericht Dortmund, HRB 20621

Vorstand: Jens Wagener (Vors.), Wolfgang Neuhaus, Dr. Georg Pietrek, Jens 
Trompeter, Sebastian Neus

Aufsichtsrat: Prof. Dr. Burkhard Igel (Vors.), Michael Neuhaus, Jennifer 
Fiorentino





signature.asc
Description: Message signed with OpenPGP using GPGMail
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Late discovery of a breaking change in Equinox that impacts Equinox hook implementations

2015-05-29 Thread Thomas Watson 
In Mars M6 a fix [1] went into Equinox that allows an Equinox extension 
hook implementation to return resource URLs that use a different protocol 
than the built-in bundleresource protocol.  For example, Virgo has the 
need to return the VM built-in jar or file URLs in some scenarios.  While 
doing the final testing of the Mars release candidates I found this change 
causes a breaking change in the behavior for resource URL lookups when 
equinox hooks are present which want to augment the content of the bundle 
resources [2].  This must be fixed for Mars in my opinion.  But in order 
to fix this any equinox extension hooks that want to change the protocol 
used for resource URLs will need to override a different method.  For more 
information please see [2]. 

Unfortunately this change is not available in RC3, but this late change 
impacts a very small number of projects.  I really only know of it 
impacting Virgo.  Please comment in the bug [2] if you have concerns.

Tom

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=460637
[2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=468817
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Mars RC2 is now available (except Mac EPP packages delayed a little)

2015-05-29 Thread David M Williams 
The built-in repository site of .../releases/mars now has RC2 content 
(along with RC1, and M7). 

The EPP packages will be available soon, or later today, for Windows and 
Linux, at the usual site of 

http://www.eclipse.org/downloads/index-developer-installer.php

The "Mac Packages" are being withheld for now, while a signing issue is 
investigated (bug 468598). It is believed that they can be available on 
Monday, but we thought best to make sure we at least understood the 
signing issue, if not actual fix it for RC2. 

Thanks to all who have made this Release Candidate possible. 

___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev