getProjectTriggering job error solved #1544
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Ginxo
force-pushed
the
project_triggering_job_error
branch
8 times, most recently
from
131b057
to
665ed9b
Compare
Ginxo
force-pushed
the
project_triggering_job_error
branch
from
665ed9b
to
a4bb4c2
Compare
mbiarnes
reviewed
Dec 2, 2020
|
Jenkins run fdb |
|
Jenkins run cdb |
|
Jenkins execute product fdb |
|
Jenkins run upstream |
|
@mbiarnes tests performed
|
mbiarnes
approved these changes
Dec 2, 2020
mariofusco
approved these changes
Dec 9, 2020
Ginxo
added a commit
to Ginxo/droolsjbpm-build-bootstrap
that referenced
this pull request
Jan 26, 2021
* [JBPM-9399] Add support to jBPM and runtime/cluster environments detection * generate files flow (kiegroup#1551) * getProjectTriggering job error solved (kiegroup#1544) * getProjectTriggering job error solved * testing generate_files.yml error * kie-wb-common should not depend on kie-wb-playground (kiegroup#1550) * JBPM-9505: Drop Case Management (Tech Preview) editor (kiegroup#1541) * Update build chain files (kiegroup#1555) Co-authored-by: mareknovotny <mareknovotny@users.noreply.github.com> * Revert "kie-wb-common should not depend on kie-wb-playground (kiegroup#1550)" (kiegroup#1558) This reverts commit 789495d. * Update build chain files (kiegroup#1559) Co-authored-by: mareknovotny <mareknovotny@users.noreply.github.com> * [DROOLS-5860] Updating poms (kiegroup#1560) * [DROOLS-5860] Declaring/updating dependencies * [DROOLS-5860] Renamed module as per PR request * [DROOLS-5860] Declaring kie-pmml-dependencies version * [DROOLS-5860] Fix poms * bump mvel to version 2.4.11.Final (kiegroup#1561) * upgraded to 7.49.0-SNAPSHOT * Bump version.com.thoughtworks.xstream from 1.4.14 to 1.4.15 (kiegroup#1562) Bumps `version.com.thoughtworks.xstream` from 1.4.14 to 1.4.15. Updates `xstream` from 1.4.14 to 1.4.15 - [Release notes](https://github.com/x-stream/xstream/releases) - [Commits](https://github.com/x-stream/xstream/commits) Updates `xstream-hibernate` from 1.4.14 to 1.4.15 - [Release notes](https://github.com/x-stream/xstream/releases) - [Commits](https://github.com/x-stream/xstream/commits) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * JBPM-9542: Remove issue-keeper tool (kiegroup#1563) Due to recent jira authentication changes we decided to stop using issue-keeper tool for preventing test method run. It was replaced by simple '@ignore' junit annotations. For more details see: - https://issues.redhat.com/browse/JBPM-9542 - https://github.com/ibek/issue-keeper * Fixing broken upstream repository deps for kie-wb-common (kiegroup#1568) * Update build chain files (kiegroup#1569) Co-authored-by: Ginxo <Ginxo@users.noreply.github.com> * fixed removal commands in shell scripts (kiegroup#1571) * upgrade to mvel 2.4.12.Final (kiegroup#1570) * [JBPM-9557] Enable sb keycloak test with testcontainers (kiegroup#1567) * Jenkinsfile.buildchain tools replaced by nodejs (kiegroup#1572) * [ISSUE 126] --skipParallelCheckout added to Jenkinsfile.builchain (kiegroup#1574) * BXMSPROD-1124: changed upload scripts of binaries to filemgmt.jboss.org to exclude droolsjbpm-tools" (kiegroup#1556) * [JBPM-9549] Upgrade SpringBoot to 2.3.4 (kiegroup#1565) * Update project-dependencies.yaml (kiegroup#1573) Removal of droolsjbpm-tools repository from community build * Update build chain files (kiegroup#1575) Co-authored-by: mbiarnes <mbiarnes@users.noreply.github.com> * BXMSPROD-1144 test 1 * BXMSPROD-1144 test 2 Co-authored-by: egonzale <egonzale@redhat.com> Co-authored-by: Kirill Gaevskii <kgaevski@redhat.com> Co-authored-by: Roger Martínez <roger600@gmail.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: mareknovotny <mareknovotny@users.noreply.github.com> Co-authored-by: Marek Novotný <hotmana76@gmail.com> Co-authored-by: Gabriele Cardosi <gabriele.cardosi@gmail.com> Co-authored-by: Mario Fusco <mario.fusco@gmail.com> Co-authored-by: Michael Biarnes Kiefer <mbiarnes@redhat.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Jozef Marko <jomarko@redhat.com> Co-authored-by: Ginxo <Ginxo@users.noreply.github.com> Co-authored-by: Gonzalo Muñoz <gmunozfe@redhat.com> Co-authored-by: mbiarnes <mbiarnes@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thank you for submitting this pull request
I would have to find alternatives to "Build Chain Generate Files / File Generation" from a forked project. Meanwhile please consider the solution for the getProjectTriggering problem and I will treat "Build Chain Generate Files / File Generation" in a different one.
How to retest this PR or trigger a specific build:
a pull request please add comment: Jenkins retest this
a full downstream build please add comment: Jenkins run fdb
a compile downstream build please add comment: Jenkins run cdb
a full production downstream build please add comment: Jenkins execute product fdb
an upstream build please add comment: Jenkins run upstream