[
https://issues.apache.org/jira/browse/HBASE-21690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated HBASE-21690:
--------------------------------
Description:
Looking back at our Jenkinsfile I just realized why we're running Nightlies
every day for all branches regardless of changes. We use this stanza:
{code}
triggers {
cron('@daily')
}
{code}
It should probably be a daily check to see if the branch has changed. That
would alleviate both my own concerns about stale feature branches and some of
the infra concerns about how many build slots we've been using.
If possible, having a "build once a week (or month) even if there have been no
changes" would be nice, but I haven't looked at the Jenkins Pipeline DSL in a
while so I can't remember if the set of triggers is an OR.
relevant docs:
https://jenkins.io/doc/book/pipeline/syntax/#triggers
was:
Looking back at our Jenkinsfile I just realized why we're running Nightlies
every day for all branches regardless of changes. We use this stanza:
{code}
triggers {
cron('@daily')
}
{code}
If should probably be a daily check to see if the branch has changed. That
would alleviate both my own concerns about stale feature branches and some of
the infra concerns about how many build slots we've been using.
If possible, having a "build once a week (or month) even if there have been no
changes" would be nice, but I haven't looked at the Jenkins Pipeline DSL in a
while so I can't remember if the set of triggers is an OR.
relevant docs:
https://jenkins.io/doc/book/pipeline/syntax/#triggers
> Nightly jobs should only trigger daily if there have been SCM changes
> ---------------------------------------------------------------------
>
> Key: HBASE-21690
> URL: https://issues.apache.org/jira/browse/HBASE-21690
> Project: HBase
> Issue Type: Task
> Components: test
> Reporter: Sean Busbey
> Priority: Major
>
> Looking back at our Jenkinsfile I just realized why we're running Nightlies
> every day for all branches regardless of changes. We use this stanza:
> {code}
> triggers {
> cron('@daily')
> }
> {code}
> It should probably be a daily check to see if the branch has changed. That
> would alleviate both my own concerns about stale feature branches and some of
> the infra concerns about how many build slots we've been using.
> If possible, having a "build once a week (or month) even if there have been
> no changes" would be nice, but I haven't looked at the Jenkins Pipeline DSL
> in a while so I can't remember if the set of triggers is an OR.
> relevant docs:
> https://jenkins.io/doc/book/pipeline/syntax/#triggers
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
