Project

Profile

Help

Task #965

As a user, I can see all Jenkins stuff as public information

Added by bmbouter over 5 years ago. Updated over 1 year ago.

Status:
CLOSED - COMPLETE
Priority:
Normal
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
Yes
Tags:
Pulp 2
Sprint:
Sprint 18
Quarter:

Description

Currently the Jenkins infrastructure is not publicly visible. This story is to set up a 'jenkins' directory under https://pulpadmin.fedorapeople.org. This directory will host static files with Jenkins build results. The build results will be published to https://pulpadmin.fedorapeople.org/jenkins using the Publish Over SSH Plugin[0].

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

1) publish the output of the job to https://pulpadmin.fedorapeople.org/jenkins
2) run some bash commands on pulpadmin.fedorapeople.org/jenkins to delete older build outputs

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

For Pull Request jobs, the GitHub Pull Request Builder Plugin should be used to comment on the PR. The comment should contain a link to the build results published to https://pulpadmin.fedorapeople.org/jenkins

This step can be accomplished with a JJB definition found here[2].

[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
[2] https://docs.openstack.org/infra/jenkins-job-builder/triggers.html?highlight=pull%20request#triggers.github-pull-request

Add a section to the Pulp docs that links to useful pages on https://pulpadmin.fedorapeople.org


Checklist

History

#1 Updated by bmbouter over 3 years ago

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?).

#2 Updated by dkliban@redhat.com over 3 years ago

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

#3 Updated by semyers over 3 years ago

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.

#4 Updated by dkliban@redhat.com over 3 years ago

  • Description updated (diff)
  • Sprint Candidate changed from No to Yes

#5 Updated by dkliban@redhat.com over 3 years ago

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.

#6 Updated by mhrivnak over 3 years ago

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?

#7 Updated by bmbouter over 3 years ago

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/

#8 Updated by dkliban@redhat.com over 3 years ago

  • Description updated (diff)

#9 Updated by bmbouter over 3 years ago

I added some checklist items

#10 Updated by bmbouter over 3 years ago

  • Groomed changed from No to Yes

After review I'm marking the story as groomed. I want this added to the sprint because upstream contributors cannot see the failures on their own PRs. We have 1 contributor blocked on this right now.

#11 Updated by bmbouter over 3 years ago

  • Sprint/Milestone set to 36

Added to sprint per discussion w/ mhrivnak, @jalberts, @smyers, @dkliban

#12 Updated by dkliban@redhat.com over 3 years ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to dkliban@redhat.com

#13 Updated by mhrivnak over 3 years ago

  • Sprint/Milestone changed from 36 to 37

#14 Updated by dkliban@redhat.com over 3 years ago

  • Tracker changed from Story to Task
  • Status changed from ASSIGNED to CLOSED - COMPLETE

#15 Updated by bmbouter over 2 years ago

  • Sprint set to Sprint 18

#16 Updated by bmbouter over 2 years ago

  • Sprint/Milestone deleted (37)

#17 Updated by bmbouter over 1 year ago

  • Tags Pulp 2 added

Please register to edit this issue

Also available in: Atom PDF