15:13:12 <Krinkle> James_F: Looks like jsduck/doxygen stopped running on tags 15:13:13 <Krinkle> https://doc.wikimedia.org/mediawiki-core/ 15:13:25 <Krinkle> stopped at 1.30.0 and non-zero times for REL1_32 15:13:43 <Krinkle> REL1_33 as well. 15:13:46 <Krinkle> So I guess the branch trigger is working 15:13:49 <Krinkle> but tag stopped 15:14:27 <Krinkle> https://github.com/wikimedia/integration-config/commit/8f9b3528176eca6c60dee0bb8b2c65a3cd21ba2a 15:14:28 <Krinkle> Aha 15:14:38 <Krinkle> It was changed from postmerge/publish to an hourly cron 15:14:42 <Krinkle> which watches branches only
eek, note the job is explicitly made to NOT process tags. Either because I could not figure out how to trigger on tag change or I considered that having document per branch was sufficient.
From what I can tell, it should work just fine to use the same job for postmerge as for publish.
The code we use to compute DOC_SUBPATH (e.g. "master", "REL1_34" or "1.2.3") already supports refs/tags/.*.
I tried this out for unicodejs, which publishes to https://doc.wikimedia.org/unicodejs/ but has stopped working 2 years ago. The last doc publish was for v0.2.0 but there has since been v0.2.2 and v12.0.0.
I replayed the Gerrit event on contint1001 that created one of these newer tags, like so:
krinkle@contint1001:~$ zuul enqueue-ref --trigger gerrit --pipeline publish --project unicodejs --ref 'refs/tags/v0.2.2' --newrev '2b81e56f2da9c8d33c2ca1d0670d41d8a06b0716' --oldrev '0000000000000000000000000000000000000000'
This correctly triggered the job at https://integration.wikimedia.org/ci/job/generic-node10-docs-docker-publish/57/console.
However, it fails early when Castor runs, due to unconditionally using ZUUL_BRANCH:
+ exec docker run … docker-registry.wikimedia.org/releng/castor:0.2.3 load … castor/castor-define-namespace.bash: line 7: ZUUL_BRANCH: unbound variable
I temporarily edited the generic-node10-docs-docker-publish job in the Jenkins administration to set ZUUL_BRANCH to see if this is the only issue. After setting it and replaying the event again, it works as expected:
Mentioned in SAL (#wikimedia-releng) [2019-10-26T20:47:17Z] <Krinkle> krinkle@contint1001$ zuul enqueue-ref --trigger gerrit --pipeline publish --project unicodejs --ref 'refs/tags/v12.0.0' --newrev '63ab6302019d3b6b1b762b5c0094370e3030e94c' --oldrev '0000000000000000000000000000000000000000' for T232055
The Castor issue is fixed, and – Tag published documentation now works fine for library repos!
Next: MediaWiki core.
The mediawiki-core-jsduck-docker-publish job isn't starting when I replay a mediawiki/core git tag event because it is rejected by its branch filter in zuul/layout.yaml:
jobs: - name: mediawiki-core-jsduck-docker-publish branch: ^(REL.*|master)$ projects: - name: mediawiki/core postmerge: - mediawiki-core-jsduck-docker-publish publish: - mediawiki-core-jsduck-docker-publish
This is because implicit in having a branch filter, Zuul also rejects any event that does not have a change.branch attribute. To fix this, I have converted it to a skip-if filter. So instead of only allowing events that have a branch and match the filter, it will now only reject events that have a branch and match the filter.
- name: mediawiki-core-jsduck-docker-publish skip-if: - branch: ^wmf/.*$
Mentioned in SAL (#wikimedia-releng) [2019-10-26T21:25:51Z] <Krinkle> krinkle@contint zuul enqueue-ref --trigger gerrit --pipeline publish --project mediawiki/core --ref 'refs/tags/1.30.1' --newrev 'a0b31d95610c8f415a2cc29349cdbf14c23c7d4b' --oldrev '0000000000000000000000000000000000000000' for T232055