Patch Set 7: Code-Review+2 Verified+1
ah, waiting for me ... ok then. Let's do any tweaks later, not like merging
this changes anything on jenkins in itself.
--
To view, visit https://gerrit.osmocom.org/3911
To unsubscribe, visit https://gerrit.osmocom.org/settings
Gerrit-MessageType:
Neels Hofmeyr has submitted this change and it was merged.
Change subject: Gerrit verification jobs as Jenkins Job Builder YAML [1] file.
..
Gerrit verification jobs as Jenkins Job Builder YAML [1] file.
All jobs are in jobs/
Patch Set 7: Code-Review+1
I'm all for moving this ahead, leaving it up to Neels to decide when this is +2
and should be merged
--
To view, visit https://gerrit.osmocom.org/3911
To unsubscribe, visit https://gerrit.osmocom.org/settings
Gerrit-MessageType: comment
Gerrit-Change-Id:
Patch Set 7:
(1 comment)
Sorry for noise by several patchsets because of typos...
https://gerrit.osmocom.org/#/c/3911/7/jobs/gerrit-verifications.yml
File jobs/gerrit-verifications.yml:
PS7, Line 222: clean:
:before: true
... instead of "clean state" shell step
--
Hello Neels Hofmeyr,
I'd like you to reexamine a change. Please visit
https://gerrit.osmocom.org/3911
to look at the new patch set (#6).
Gerrit verification jobs as Jenkins Job Builder YAML [1] file.
All jobs are in jobs/ directory and will be automatically verified and
deployed in a
Hello Neels Hofmeyr,
I'd like you to reexamine a change. Please visit
https://gerrit.osmocom.org/3911
to look at the new patch set (#5).
Gerrit verification jobs as Jenkins Job Builder YAML [1] file.
[1] https://docs.openstack.org/infra/jenkins-job-builder/
Change-Id:
Patch Set 4:
(9 comments)
Thanks for the review, all comments/changes will be applied. Let's submit/merge
afterwards!
>> and let's add a jobs/README that describes how these yml
>> files are used to update our jenkins jobs
Good idea, will be done. I also would like to move lynxis
Patch Set 4:
and let's add a jobs/README that describes how these yml files are used to
update our jenkins jobs
--
To view, visit https://gerrit.osmocom.org/3911
To unsubscribe, visit https://gerrit.osmocom.org/settings
Gerrit-MessageType: comment
Gerrit-Change-Id:
Patch Set 4:
(2 comments)
https://gerrit.osmocom.org/#/c/3911/4/jobs/gerrit-verifications.yml
File jobs/gerrit-verifications.yml:
Line 246: - branch-compare-type: 'ANT'
ANT? that's the web UI's 'Path' value?
Line 261: - shell: 'chmod -R +w *; rm -rf *; git checkout .'
Patch Set 4: Code-Review+2
(7 comments)
all of these can be addressed after this is merged.
https://gerrit.osmocom.org/#/c/3911/4/jobs/gerrit-verifications.yml
File jobs/gerrit-verifications.yml:
Line 3:# following default values can be overridden by each repo
by repo you mean the
Gerrit verification jobs as Jenkins Job Builder YAML [1] file.
[1] https://docs.openstack.org/infra/jenkins-job-builder/
Change-Id: I04387367a6e2d737bfb50423c81a8908d3c2a89f
---
A jobs/gerrit-verifications.yml
1 file changed, 268 insertions(+), 0 deletions(-)
git pull
Gerrit verification jobs as Jenkins Job Builder YAML [1] file.
[1] https://docs.openstack.org/infra/jenkins-job-builder/
Change-Id: I04387367a6e2d737bfb50423c81a8908d3c2a89f
---
A jobs/gerrit-verifications.yml
1 file changed, 273 insertions(+), 0 deletions(-)
git pull
Patch Set 1:
(1 comment)
Of course, we can remove jobs which raise questions, but they may just point
out "unwanted" deviations e.g. compiler warnings v3/v4.
Which jobs should be removed in your opinion?
https://gerrit.osmocom.org/#/c/3911/1/jobs/gerrit-verifications.yml
File
Patch Set 1:
(1 comment)
I think it would be easier to introduce this gradually - for example first add
all the jobs which do not raise questions, make sure it works as expected and
than add the remaining one, clarifying stuff on a case-by-case basis.
Review at https://gerrit.osmocom.org/3911
Gerrit verification jobs as Jenkins Job Builder YAML [1] file.
[1] https://docs.openstack.org/infra/jenkins-job-builder/
Change-Id: I04387367a6e2d737bfb50423c81a8908d3c2a89f
---
A jobs/gerrit-verifications.yml
1 file changed, 288 insertions(+), 0
15 matches
Mail list logo
