Pulp

We need to do something about this. We have new contributors asking for 'the output of the jenkins job' in order for them to fix their PRs. Can we put some ideas/options here?

One idea is to scp the console output logs for each platform for each build to a webhost (openshift?). That would be a good near-term option, but it would not allow a community user to inspect the pulp-smash failures (or would it?).

We should try to host the results of jenkins builds on OpenShift. This requires creating a new application in OpenShift. We should point a jenkins.pulproject.org to this application.

Each job that we want to publish results for should use the Publish Over SSH Plugin[0] to add 2 extra build steps.

1) publish the output of the job to OpenShift
2) run some bash commands on OpenShift to delete older build outputs

These steps can be added using the docs[1] for Jenkins Job Builder.

[0] https://wiki.jenkins-ci.org/display/JENKINS/Publish+Over+SSH+Plugin
[1] https://docs.openstack.org/infra/jenkins-job-builder/builders.html#builders.publish-over-ssh

dkliban@redhat.com wrote:

We should try to host the results of jenkins builds on OpenShift. This requires creating a new application in OpenShift. We should point a jenkins.pulproject.org to this application.

This seems like a better approach than what's in the original story. Something that I think might be tricky is getting jenkins to post links on github to the openshift results instead of the normal link back to jenkins.

We should be able to get around the linking problem by having the SSH publish plugin create an environment variable containing the link to the results. Then the PR builder plugin can use that variable to form the message that it posts back to github.

Since it's just static files we need to host, is there a static file service we could use instead of an application deployment and orchestration system? Perhaps Fedora has something we could use, such as fedorapeople.org ? The fact that Openshift is overkill isn't a deal breaker of course, but it's worth considering other options.

Another factor is that Openshift Online v2, the one we're currently using and the only one available at the moment for production use, is planned to be phased out as v3 takes its place. There's no timeline for it yet, but if we have an opportunity to use something simpler right now, that could save us from having to switch in the future.

What do you think?

We could use the same space that we host the IRC meeting logs. Currently those are hosted here: https://pulpadmin.fedorapeople.org/triage/pulp-dev/?C=N;O=D

I like ^ because it's not the same repo as we distribute our bits through.

I like the branding creating with a site like jenkins.pulpproject.org. If we do launch that URL, I would want it to be more than just logs. I would want it to be a place that you can see the health of Pulp via a dashboard. Something kind of like what Qpid has http://concordia.usersys.redhat.com:56720/

I added some checklist items