Indeed, the component builds are not integration builds.
cW
On 3 June, 2016 at 09:04:52, Ernesto Posse (eposse@xxxxxxxxxxxxx) wrote:
If those are the new
Papyrus-RT-Integration-<Component> jobs, then they are
already configured to poll every 15 minutes.
But I'm now confused with the name of those jobs, if we are
going to have *weekly* integration builds as we discussed.
They should, if they aren’t already.
On 3 June, 2016 at 09:00:15, Ernesto Posse (eposse@xxxxxxxxxxxxx) wrote:
And those component builds would also be
polling every 15 minutes?
Wouldn’t it make more sense for this build to be a downstream
build of all of the component builds, so that it is triggered
whenever one of them produces a new build? Because its
purpose is to re-package the binaries produced by those
builds.
Otherwise, if it is triggered by source changes, it will
be triggered at the same time as the component builds and so will
always be lagging behind them in its content.
cW
On 3 June, 2016 at 08:45:35, Ernesto Posse (eposse@xxxxxxxxxxxxx) wrote:
I just checked the configuration for
this job and it is set to poll every 15 minutes, so I expect this
should work for you. I've added you to the list of users that can
configure this job. I think you should be able to see it now.
(https://hudson.eclipse.org/papyrus-rt/job/Papyrus-RT-Product/)
By the way, we are also planning a more stable weekly
integration build repo which could be used to make sure that the
developer and tester setup models don't throw errors when trying to
access the repo.
Hi,
Thanks for the
feedback Ernesto!
What about the
update frequency for this update site then? Has it the same poll
frequency checking for merges to the master branch as the previous
one, i.e. 20 minutes? Or is this new update site updated less
frequently, time triggered as true 24-hour nightly build? We (at
least I) really need an update site that is updated often to able
to provide quick feedback if needed. I don't want to wait until
next day to be able to get the latest build of
Papyrus-RT.
I can't see the
build configuration for this new build (as I can for the other one
since I got permissions to be able to retrigger that job in case it
had failed, which I won't be able to do for this new job
then).
_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
|