You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@yetus.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2018/12/20 05:30:00 UTC

[jira] [Commented] (YETUS-738) Some Jenkinsfile improvements

    [ https://issues.apache.org/jira/browse/YETUS-738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16725596#comment-16725596 ] 

Allen Wittenauer commented on YETUS-738:
----------------------------------------

bq. Attempt to merge precommit-yetus-admin features to see if we can do it all in one

precommit-admin uses curl to "remotely" HTTP connect to Jenkins via URLs. Part of that URL (besides the job URL) is the token required for authentication. The token on each job is set from the Build Triggers and specifically from 'Trigger builds remotely (e.g., from scripts)' option.  It doesn't appear to be possible to set this in Multi-branch Pipeline job.  Perhaps [~abayer] has some hints, but my guess is that we're going to be stuck with two jobs at least for the short term. :(

> Some Jenkinsfile improvements
> -----------------------------
>
>                 Key: YETUS-738
>                 URL: https://issues.apache.org/jira/browse/YETUS-738
>             Project: Yetus
>          Issue Type: Improvement
>          Components: build
>            Reporter: Allen Wittenauer
>            Priority: Major
>
> A few things to do:
> * Add JIRA username/password
> * Write results to github
> * Attempt to merge precommit-yetus-admin features to see if we can do it all in one
> * Drop the yetus-qbt report email with the the full reports that the Jenkinsfile does
> * add sentinel
> * add personality (might be blocked on YETUS-721)
> * disable email notification for PRs (INFRA-17471 should enable PR status on github)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)