Minor In my pipeline I have an implicitly loaded library and a non-standard project factory (`inline-pipeline` but reproducible with `pipeline-multibranch-defaults` too).
When I do `checkout scm` - the in-progress event not being sent.
I did the following as the very first step in my pipeline:
@NonCPS
def test() {
echo currentBuild.rawBuild.getAction(com.cloudbees.jenkins.plugins.bitbucket.FirstCheckoutCompletedInvisibleAction.class).toString()
}
And I can see a non-null echo message in the build log.
I think because in non-standard project factory it doesn't try to fetch a `Jenkinsfile` - the first ever checkout happening to the library and setting `FirstCheckoutCompletedInvisibleAction`. This is not reproducible with github branch source plugin which doesn't have an analogue to that action.
- duplicates
-
JENKINS-66041 jenkins.scm.api.SCMRevisionAction not being added to the build
-
- In Review
-
- is related to
-
-
- Open
-
[JENKINS-66040] Bitbucket Server not getting notified with in-progress status when non-default project factory and a groovy library
Dee Kryvenko
created issue -
Dee Kryvenko
made changes -
| Description | Original: When I change my default project factory (Project Recognizers) from Pipeline Jenkinsfile to something else like [https://plugins.jenkins.io/inline-pipeline/] or [https://plugins.jenkins.io/pipeline-multibranch-defaults/] - no in-progress notifications being sent. Nothing in logs, both job and system logs. Failure or success statuses are stil being sent, but not in-progress. | New: When I use Project Folders and change my default project factory (Project Recognizers) from Pipeline Jenkinsfile to something else like [https://plugins.jenkins.io/inline-pipeline/] or [https://plugins.jenkins.io/pipeline-multibranch-defaults/] - no in-progress notifications being sent. Nothing in logs, both job and system logs. Failure or success statuses are still being sent, but not in-progress. |
Dee Kryvenko
made changes -
| Resolution | New: Duplicate [ 3 ] | |
| Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
Dee Kryvenko
made changes -
| Link | New: This issue duplicates JENKINS-66041 [ JENKINS-66041 ] |
Dee Kryvenko
made changes -
| Summary | Original: Bitbucket Server not getting notified with in-progress status when non-default project factory is used | New: Bitbucket Server not getting notified with in-progress status when multiple checkouts |
Dee Kryvenko
made changes -
| Resolution | Original: Duplicate [ 3 ] | |
| Status | Original: Closed [ 6 ] | New: Reopened [ 4 ] |
Dee Kryvenko
made changes -
| Description | Original: When I use Project Folders and change my default project factory (Project Recognizers) from Pipeline Jenkinsfile to something else like [https://plugins.jenkins.io/inline-pipeline/] or [https://plugins.jenkins.io/pipeline-multibranch-defaults/] - no in-progress notifications being sent. Nothing in logs, both job and system logs. Failure or success statuses are still being sent, but not in-progress. |
New:
In my pipeline I have an implicit library prohibited to override versions.
When I do `checkout scm` - the in-progress event not being sent. I did the following as the very first step: {code:java} @NonCPS def test() { echo currentBuild.rawBuild.getAction(com.cloudbees.jenkins.plugins.bitbucket.FirstCheckoutCompletedInvisibleAction.class).toString() } {code} And I can see a non-null echo message in the build log. |
Dee Kryvenko
added a comment - I've reopened it and changed description - it seems like the actual issue was in this `FirstCheckoutCompletedInvisibleAction` thing.
Dee Kryvenko
added a comment - I've reopened it and changed description - it seems like the actual issue was in this `FirstCheckoutCompletedInvisibleAction` thing. Dee Kryvenko
made changes -
| Link | New: This issue is related to JENKINS-66044 [ JENKINS-66044 ] |
Actually, closing this as I found this is due to https://issues.jenkins.io/browse/JENKINS-66041
I looked into the actions available after using that plugin and there is none that could tell the revision number, so I think it should be fixed on that plugin side.