[cross-project-issues-dev] Simrel gerrit builder is still called "photon" ? Simrel pipeline has missed 28 commits?

[Nick Boldt]

Couple quick questions for the simrel admin folks:

a) I submitted a gerrit request to update DLTK from 5.9RC4 to the latest
5.10 nightly, and it passed... but the job that ran was called "photon"
[0]. Should that job be renamed to "simrel.2018-09" instead of "photon" ?

[0]
https://ci.eclipse.org/simrel/job/simrel.photon.runaggregator.VALIDATE.gerrit/716/console


b) Then I noticed that there's a pipeline gerrit job too, but it hasn't run
for 3 days [1] and is 28 commits [2] behind master, stuck on a Modisco
change from Fabien Giquel [3]:

[1]
https://ci.eclipse.org/simrel/job/simrel.runaggregator.pipeline.gerrit/7/
[2] https://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/log/
[3]
https://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/commit/?id=5505415a55131a38a042d6a2fbe4982fb9d5997d

So... should that be running more often?

If you'd like me to have a look at the job configs, please grant me access
and I will investigate further. Maybe it's not set to run via a cron /
check github for changes?
--
Nick Boldt

Principal Software Engineer, RHCSA

Productization Lead :: JBoss Tools & Dev Studio

IM: @nickboldt / @nboldt / http://nick.divbyzero.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
@ @redhatnews <https://twitter.com/redhatnews> Red Hat
<https://www.facebook.com/RedHatInc>
<https://www.facebook.com/RedHatInc>


“The Only Thing That Is Constant Is Change” - Heraclitus

[Nick Boldt]

Worse... I just noticed that the simrel gerrit validator is using Eclipse
4.8 not 4.9, so it's validating the wrong baseline. See the section [4]
labelled "*tycho-eclipserun-plugin:1.0.0:eclipse-run (validate-repo) @
build*" for more details.

[4]
https://ci.eclipse.org/simrel/job/simrel.photon.runaggregator.VALIDATE.gerrit/719/consoleFull

Post by Nick Boldt
a) I submitted a gerrit request to update DLTK from 5.9RC4 to the latest
5.10 nightly, and it passed... but the job that ran was called "photon"
[0]. Should that job be renamed to "simrel.2018-09" instead of "photon" ?
[0]
https://ci.eclipse.org/simrel/job/simrel.photon.runaggregator.VALIDATE.gerrit/716/console
b) Then I noticed that there's a pipeline gerrit job too, but it hasn't
run for 3 days [1] and is 28 commits [2] behind master, stuck on a Modisco
[1]
https://ci.eclipse.org/simrel/job/simrel.runaggregator.pipeline.gerrit/7/
[2] https://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/log/
[3]
https://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/commit/?id=5505415a55131a38a042d6a2fbe4982fb9d5997d
So... should that be running more often?
If you'd like me to have a look at the job configs, please grant me access
and I will investigate further. Maybe it's not set to run via a cron /
check github for changes?
--
Nick Boldt
Principal Software Engineer, RHCSA
Productization Lead :: JBoss Tools & Dev Studio
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
@ @redhatnews <https://twitter.com/redhatnews> Red Hat
<https://www.facebook.com/RedHatInc>
<https://www.facebook.com/RedHatInc>
“The Only Thing That Is Constant Is Change” - Heraclitus

--
Nick Boldt

Principal Software Engineer, RHCSA

Productization Lead :: JBoss Tools & Dev Studio

IM: @nickboldt / @nboldt / http://nick.divbyzero.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
@ @redhatnews <https://twitter.com/redhatnews> Red Hat
<https://www.facebook.com/RedHatInc>
<https://www.facebook.com/RedHatInc>


“The Only Thing That Is Constant Is Change” - Heraclitus

[Frederic Gurr]

Hi,

AFAIK this works as expected. The baseline is the latest stable release.
In that case Photon GA.

Regards,

Fred

Post by Nick Boldt
Worse... I just noticed that the simrel gerrit validator is using
Eclipse 4.8 not 4.9, so it's validating the wrong baseline. See the
section [4] labelled "*tycho-eclipserun-plugin:1.0.0:eclipse-run
[4]
https://ci.eclipse.org/simrel/job/simrel.photon.runaggregator.VALIDATE.gerrit/719/consoleFull
a) I submitted a gerrit request to update DLTK from 5.9RC4 to the
latest 5.10 nightly, and it passed... but the job that ran was
called "photon" [0]. Should that job be renamed to "simrel.2018-09"
instead of "photon" ?
[0]
https://ci.eclipse.org/simrel/job/simrel.photon.runaggregator.VALIDATE.gerrit/716/console 
b) Then I noticed that there's a pipeline gerrit job too, but it
hasn't run for 3 days [1] and is 28 commits [2] behind master, stuck
[1]
https://ci.eclipse.org/simrel/job/simrel.runaggregator.pipeline.gerrit/7/
[2] https://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/log/
[3] https://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/commit/?id=5505415a55131a38a042d6a2fbe4982fb9d5997d
So... should that be running more often?
If you'd like me to have a look at the job configs, please grant me
access and I will investigate further. Maybe it's not set to run via
a cron / check github for changes? 
--
Nick Boldt
Principal Software Engineer, RHCSA
Productization Lead :: JBoss Tools & Dev Studio
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
@ @redhatnews <https://twitter.com/redhatnews>     Red Hat
<https://www.facebook.com/RedHatInc>
<https://www.facebook.com/RedHatInc>
“The Only Thing That Is Constant Is Change” - Heraclitus
--
Nick Boldt
Principal Software Engineer, RHCSA
Productization Lead :: JBoss Tools & Dev Studio
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
@ @redhatnews <https://twitter.com/redhatnews>     Red Hat
<https://www.facebook.com/RedHatInc>
<https://www.facebook.com/RedHatInc>
“The Only Thing That Is Constant Is Change” - Heraclitus
_______________________________________________
cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[Nick Boldt]

OK. Wasn't clear to me from the log if that was a baseline check, or a 'use
this version of Eclipse to perform some assembly' task.

eclipse-run: sounds like a run
validate-repo: sounds like a baseline check?
@ build: ok, now it sounds like a build step again.

(I"m just saying Maven can be confusing sometimes. I recommend always
adding a `-V` flag when building too, so you know what version of Maven /
JDK is used.)

Cheers,

Nick


On Thu, Aug 30, 2018 at 11:40 AM Frederic Gurr <

Hi,
AFAIK this works as expected. The baseline is the latest stable release.
In that case Photon GA.
Regards,
Fred

Post by Nick Boldt
Worse... I just noticed that the simrel gerrit validator is using
Eclipse 4.8 not 4.9, so it's validating the wrong baseline. See the
section [4] labelled "*tycho-eclipserun-plugin:1.0.0:eclipse-run
[4]

https://ci.eclipse.org/simrel/job/simrel.photon.runaggregator.VALIDATE.gerrit/719/consoleFull

Post by Nick Boldt
a) I submitted a gerrit request to update DLTK from 5.9RC4 to the
latest 5.10 nightly, and it passed... but the job that ran was
called "photon" [0]. Should that job be renamed to "simrel.2018-09"
instead of "photon" ?
[0]

https://ci.eclipse.org/simrel/job/simrel.photon.runaggregator.VALIDATE.gerrit/716/console

Post by Nick Boldt
b) Then I noticed that there's a pipeline gerrit job too, but it
hasn't run for 3 days [1] and is 28 commits [2] behind master, stuck
[1]

https://ci.eclipse.org/simrel/job/simrel.runaggregator.pipeline.gerrit/7/

Post by Nick Boldt
[2]

https://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/log/

Post by Nick Boldt
[3]

https://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/commit/?id=5505415a55131a38a042d6a2fbe4982fb9d5997d

Post by Nick Boldt
So... should that be running more often?
If you'd like me to have a look at the job configs, please grant me
access and I will investigate further. Maybe it's not set to run via
a cron / check github for changes?
--
Nick Boldt
Principal Software Engineer, RHCSA
Productization Lead :: JBoss Tools & Dev Studio
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
@ @redhatnews <https://twitter.com/redhatnews> Red Hat
<https://www.facebook.com/RedHatInc>
<https://www.facebook.com/RedHatInc>
“The Only Thing That Is Constant Is Change” - Heraclitus
--
Nick Boldt
Principal Software Engineer, RHCSA
Productization Lead :: JBoss Tools & Dev Studio
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
@ @redhatnews <https://twitter.com/redhatnews> Red Hat
<https://www.facebook.com/RedHatInc>
<https://www.facebook.com/RedHatInc>
“The Only Thing That Is Constant Is Change” - Heraclitus
_______________________________________________
cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe

from this list, visit

Post by Nick Boldt
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

--
Frederic Gurr
Release Engineer | Eclipse Foundation Europe GmbH
Annastr. 44, D-64673 Zwingenberg
Handelsregister: Darmstadt HRB 92821
Managing Directors: Ralph Mueller, Mike Milinkovich, Chris Laroque
_______________________________________________
cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

--
Nick Boldt

Principal Software Engineer, RHCSA

Productization Lead :: JBoss Tools & Dev Studio

IM: @nickboldt / @nboldt / http://nick.divbyzero.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
@ @redhatnews <https://twitter.com/redhatnews> Red Hat
<https://www.facebook.com/RedHatInc>
<https://www.facebook.com/RedHatInc>


“The Only Thing That Is Constant Is Change” - Heraclitus

[Ed Willink]

Hi

https://hudson.eclipse.org/simrel/job/simrel.runaggregator.pipeline/
seems to be ticking over nicely.

    Regards

        Ed Willink

Post by Nick Boldt
a) I submitted a gerrit request to update DLTK from 5.9RC4 to the
latest 5.10 nightly, and it passed... but the job that ran was called
"photon" [0]. Should that job be renamed to "simrel.2018-09" instead
of "photon" ?
[0]
https://ci.eclipse.org/simrel/job/simrel.photon.runaggregator.VALIDATE.gerrit/716/console
b) Then I noticed that there's a pipeline gerrit job too, but it
hasn't run for 3 days [1] and is 28 commits [2] behind master, stuck
[1]
https://ci.eclipse.org/simrel/job/simrel.runaggregator.pipeline.gerrit/7/
[2] https://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/log/
[3]
https://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/commit/?id=5505415a55131a38a042d6a2fbe4982fb9d5997d
So... should that be running more often?
If you'd like me to have a look at the job configs, please grant me
access and I will investigate further. Maybe it's not set to run via a
cron / check github for changes?
--
Nick Boldt
Principal Software Engineer, RHCSA
Productization Lead :: JBoss Tools & Dev Studio
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
@ @redhatnews <https://twitter.com/redhatnews>    Red Hat
<https://www.facebook.com/RedHatInc>
<https://www.facebook.com/RedHatInc>
“The Only Thing That Is Constant Is Change” - Heraclitus
_______________________________________________
cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

[Frederic Gurr]

Hi,

Post by Nick Boldt
a) I submitted a gerrit request to update DLTK from 5.9RC4 to the latest
5.10 nightly, and it passed... but the job that ran was called "photon"
[0]. Should that job be renamed to "simrel.2018-09" instead of "photon" ?
[0]
https://ci.eclipse.org/simrel/job/simrel.photon.runaggregator.VALIDATE.gerrit/716/console 

You are right, it should be renamed. The goal was to replace it with the
pipeline Gerrit job... unfortunately that one is not working as expected
yet (see below). I've renamed (actually copied & renamed) it to reduce
confusion.

Post by Nick Boldt
b) Then I noticed that there's a pipeline gerrit job too, but it hasn't
run for 3 days [1] and is 28 commits [2] behind master, stuck on a
[1]
https://ci.eclipse.org/simrel/job/simrel.runaggregator.pipeline.gerrit/7/
[2] https://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/log/
[3] https://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/commit/?id=5505415a55131a38a042d6a2fbe4982fb9d5997d
So... should that be running more often?

It should get triggered by each Gerrit commit, but for some reason it
does not work yet. So it only runs periodically every Monday (that
was/is the sanity check for all SimRel Gerrit builds).

Post by Nick Boldt
If you'd like me to have a look at the job configs, please grant me
access and I will investigate further. Maybe it's not set to run via a
cron / check github for changes?

You now have permissions to configure
https://ci.eclipse.org/simrel/job/simrel.runaggregator.pipeline.gerrit/.
I guess an extra set of eyes might help.

Post by Nick Boldt
--
Nick Boldt
Principal Software Engineer, RHCSA
Productization Lead :: JBoss Tools & Dev Studio
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
@ @redhatnews <https://twitter.com/redhatnews>     Red Hat
<https://www.facebook.com/RedHatInc>
<https://www.facebook.com/RedHatInc>
“The Only Thing That Is Constant Is Change” - Heraclitus

Regards,

Fred

[Nick Boldt]

Four ideas for why it's not triggering:

a) you have BOTH "Gerrit event" and "Build periodically" as Build Triggers
enabled. Can both actually run when there's no gerrit info provided because
you're doing a crontab-triggered build? I guess so if it's building a
sanity-check build every monday, so maybe this isn't an issue. But surely
you'd rather have a non-gerrit, just-build-latest-in-master job run on
Mondays instead?

b) "Strategy for choosing what to build" - maybe that's not needed or
conflicts w/ the other Gerrit Trigger info?

c) there's already another gerrit-listening job enabled [1] for the repo,
so maybe only the old is being fired. If the old one is disabled/deleted,
maybe the new one will fire instead?

d) Or is there some sort of api/ssh key, handshake, etc. needed to
configure your gerrit w/ the job? Does the job need to have permissions/ACL
set up so that gerrit can trigger it?

[1]
https://ci.eclipse.org/simrel/job/simrel.photon.runaggregator.VALIDATE.gerrit/

[Nick Boldt]

OK, ignore all those suggestions.

Here's the real reason: https://stackoverflow.com/a/11525496/1661797

https://git.eclipse.org/r/#/c/128383/ -->
https://ci.eclipse.org/simrel/job/simrel.runaggregator.pipeline.gerrit/8/
--> it's running!

And yes, you can have two builds for the same gerrit trigger... as we see
here:

[image: image.png]

Post by Nick Boldt
a) you have BOTH "Gerrit event" and "Build periodically" as Build Triggers
enabled. Can both actually run when there's no gerrit info provided because
you're doing a crontab-triggered build? I guess so if it's building a
sanity-check build every monday, so maybe this isn't an issue. But surely
you'd rather have a non-gerrit, just-build-latest-in-master job run on
Mondays instead?
b) "Strategy for choosing what to build" - maybe that's not needed or
conflicts w/ the other Gerrit Trigger info?
c) there's already another gerrit-listening job enabled [1] for the repo,
so maybe only the old is being fired. If the old one is disabled/deleted,
maybe the new one will fire instead?
d) Or is there some sort of api/ssh key, handshake, etc. needed to
configure your gerrit w/ the job? Does the job need to have permissions/ACL
set up so that gerrit can trigger it?
[1]
https://ci.eclipse.org/simrel/job/simrel.photon.runaggregator.VALIDATE.gerrit/

--
Nick Boldt

Principal Software Engineer, RHCSA

Productization Lead :: JBoss Tools & Dev Studio

IM: @nickboldt / @nboldt / http://nick.divbyzero.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
@ @redhatnews <https://twitter.com/redhatnews> Red Hat
<https://www.facebook.com/RedHatInc>
<https://www.facebook.com/RedHatInc>


“The Only Thing That Is Constant Is Change” - Heraclitus

[Frederic Gurr]

Hi Nick,

Thanks for the suggestions and finding the fix!

I'll keep the old Gerrit triggered job around for a few days before I
retire it.


Regards,

Fred

OK, ignore all those suggestions. 
Here's the real reason: https://stackoverflow.com/a/11525496/1661797
https://git.eclipse.org/r/#/c/128383/
--> https://ci.eclipse.org/simrel/job/simrel.runaggregator.pipeline.gerrit/8/
--> it's running!
And yes, you can have two builds for the same gerrit trigger... as we
image.png
a) you have BOTH "Gerrit event" and "Build periodically" as Build
Triggers enabled. Can both actually run when there's no gerrit info
provided because you're doing a crontab-triggered build? I guess so
if it's building a sanity-check build every monday, so maybe this
isn't an issue. But surely you'd rather have a non-gerrit,
just-build-latest-in-master job run on Mondays instead?
b) "Strategy for choosing what to build" - maybe that's not needed
or conflicts w/ the other Gerrit Trigger info?
c) there's already another gerrit-listening job enabled [1] for the
repo, so maybe only the old is being fired. If the old one is
disabled/deleted, maybe the new one will fire instead? 
d) Or is there some sort of api/ssh key, handshake, etc. needed to
configure your gerrit w/ the job? Does the job need to have
permissions/ACL set up so that gerrit can trigger it?
[1] https://ci.eclipse.org/simrel/job/simrel.photon.runaggregator.VALIDATE.gerrit/
--
Nick Boldt
Principal Software Engineer, RHCSA
Productization Lead :: JBoss Tools & Dev Studio
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
@ @redhatnews <https://twitter.com/redhatnews>     Red Hat
<https://www.facebook.com/RedHatInc>
<https://www.facebook.com/RedHatInc>
“The Only Thing That Is Constant Is Change” - Heraclitus
_______________________________________________
cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[Nick Boldt]

No worries. Glad a quick googling of stack overflow saved the day (as it
often does). :D

On Thu, Aug 30, 2018 at 5:13 PM Frederic Gurr <

Post by Frederic Gurr
Hi Nick,
Thanks for the suggestions and finding the fix!
I'll keep the old Gerrit triggered job around for a few days before I
retire it.
Regards,
Fred

Post by Nick Boldt
OK, ignore all those suggestions.
Here's the real reason: https://stackoverflow.com/a/11525496/1661797
https://git.eclipse.org/r/#/c/128383/
-->

https://ci.eclipse.org/simrel/job/simrel.runaggregator.pipeline.gerrit/8/

Post by Nick Boldt
--> it's running!
And yes, you can have two builds for the same gerrit trigger... as we
image.png
a) you have BOTH "Gerrit event" and "Build periodically" as Build
Triggers enabled. Can both actually run when there's no gerrit info
provided because you're doing a crontab-triggered build? I guess so
if it's building a sanity-check build every monday, so maybe this
isn't an issue. But surely you'd rather have a non-gerrit,
just-build-latest-in-master job run on Mondays instead?
b) "Strategy for choosing what to build" - maybe that's not needed
or conflicts w/ the other Gerrit Trigger info?
c) there's already another gerrit-listening job enabled [1] for the
repo, so maybe only the old is being fired. If the old one is
disabled/deleted, maybe the new one will fire instead?
d) Or is there some sort of api/ssh key, handshake, etc. needed to
configure your gerrit w/ the job? Does the job need to have
permissions/ACL set up so that gerrit can trigger it?
[1]

https://ci.eclipse.org/simrel/job/simrel.photon.runaggregator.VALIDATE.gerrit/

Post by Nick Boldt
--
Nick Boldt
Principal Software Engineer, RHCSA
Productization Lead :: JBoss Tools & Dev Studio
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
@ @redhatnews <https://twitter.com/redhatnews> Red Hat
<https://www.facebook.com/RedHatInc>
<https://www.facebook.com/RedHatInc>
“The Only Thing That Is Constant Is Change” - Heraclitus
_______________________________________________
cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe

from this list, visit

Post by Nick Boldt
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

--
Frederic Gurr
Release Engineer | Eclipse Foundation Europe GmbH
Annastr. 44, D-64673 Zwingenberg
Handelsregister: Darmstadt HRB 92821
Managing Directors: Ralph Mueller, Mike Milinkovich, Chris Laroque
_______________________________________________
cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

--
Nick Boldt

Principal Software Engineer, RHCSA

Productization Lead :: JBoss Tools & Dev Studio

IM: @nickboldt / @nboldt / http://nick.divbyzero.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
@ @redhatnews <https://twitter.com/redhatnews> Red Hat
<https://www.facebook.com/RedHatInc>
<https://www.facebook.com/RedHatInc>


“The Only Thing That Is Constant Is Change” - Heraclitus