#7658 Jenkins workspace for Java SIG
Opened 2 months ago by mkoncek. Modified 5 days ago

I would like to request a Jenkins instance for the purpose of continuously building Antora documentation from the upstream sources.

More detailed information can be found here:
https://pagure.io/fedora-infrastructure/issue/7653


Metadata Update from @bstinson:
- Issue assigned to bstinson

2 months ago

Please elaborate how is this request different from #7653 ? Is the existing Jenkins project not sufficient?

In our IRC communication @bstinson mentioned that they are slowly migrating things away from that namespace and that Java SIG will have its own namespace.

Metadata Update from @kevin:
- Issue priority set to: Waiting on Assignee (was: Needs Review)

21 days ago

Is there any update here? If Fedora infrastructure is not able to handle this request then we (Java package maintainers) will need to look for a different solution for building Java packaging documentation.

@siddharthvipul1 Maybe you could help as well on this ticket?

@pingou Sadly I can't. We don't have a central master yet to provision accounts. Brian is coming with it so that both of us have access to it. I had created a ticket on bugs.centos.org for this [0]. I will ask Brian to see if this can be done in urgent.
[0] https://bugs.centos.org/view.php?id=15997

You folks should have access here via your FAS accounts:

https://jenkins-fedora-java-sig.apps.ci.centos.org/

Don't worry about maintaining plugins, or anything like that. We'll lifecycle this master image for you.

We have a few options, you can build an image and post it to dockerhub/quay.io/registry.fp.o and pull that for use in your job, or we can look at doing a custom set of images for you like we did for:
https://pagure.io/aquedoc

Metadata Update from @bstinson:
- Issue priority set to: Waiting on Reporter (was: Waiting on Assignee)

6 days ago

Thanks @bstinson
Do you know where I can find terms of use for this Jenkins instance? I'm failing to find them. I'm not very familiar with CentOS infrastructure.

Login to comment on this ticket.

Metadata