You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Pascal Schumacher <pa...@gmx.net> on 2018/03/18 11:42:23 UTC
Jenkins Pipeline Build Missing Deploy Phase?
Hello,
Jenkins successfully build camel a few hours ago, but when I try to
build only camel-core locally I get:
[INFO] Building Camel :: Core 2.22.0-SNAPSHOT
[INFO] --------------------------------[ jar
]---------------------------------
Downloading from apache.snapshots:
http://repository.apache.org/snapshots/org/apache/camel/camel-package-maven-plugin/2.22.0-SNAPSHOT/maven-metadata.xml
Downloading from apache.snapshots:
http://repository.apache.org/snapshots/org/apache/camel/camel-package-maven-plugin/2.22.0-SNAPSHOT/camel-package-maven-plugin-2.22.0-SNAPSHOT.pom
[WARNING] The POM for
org.apache.camel:camel-package-maven-plugin:jar:2.22.0-SNAPSHOT is
missing, no dependency information available
Downloading from apache.snapshots:
http://repository.apache.org/snapshots/org/apache/camel/camel-package-maven-plugin/2.22.0-SNAPSHOT/camel-package-maven-plugin-2.22.0-SNAPSHOT.jar
[ERROR] Plugin
org.apache.camel:camel-package-maven-plugin:2.22.0-SNAPSHOT or one of
its dependencies could not be resolved: Could not find artifact
org.apache.camel:camel-package-maven-plugin:jar:2.22.0-SNAPSHOT in
apache.snapshots (http://repository.apache.org/snapshots/) -> [Help 1]
https://repository.apache.org/content/groups/snapshots/org/apache/camel/apache-camel/
does not contains 2.22.0-SNAPSHOT and the build output of
https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel/job/master/139/console
does not contain any maven-deploy-plugin output.
So I guess the Jenkins pipeline build is missing the deploy phase, or
are camel-snapshot supposed to be deployed my some other means?
Cheers,
Pascal
Re: Jenkins Pipeline Build Missing Deploy Phase?
Posted by Zoran Regvart <zo...@regvart.com>.
Hello Cameleers,
I've made few refinements to the Jenkins pipeline. Now only `master`
branch's artefacts are pushed to Maven repository, and failing
Checkstyle checks no longer prevents tests from being run.
It's a good idea to keep an eye on any Checkstyle issues to have a
smoother release as those will fail release builds. A URL that you can
bookmark to see Checkstyle issues is:
https://builds.apache.org/job/Camel/job/master/lastSuccessfulBuild/checkstyleResult/
zoran
--
Zoran Regvart
Re: Jenkins Pipeline Build Missing Deploy Phase?
Posted by Zoran Regvart <zo...@regvart.com>.
Hello,
On Wed, Mar 21, 2018 at 9:04 AM, Claus Ibsen <cl...@gmail.com> wrote:
> Can we have another pipeline that just does the deploy?
> Then we can have the deploy to run once per day.
> And if we are in need of a quicker SNAPSHOT we can kick the job
> manually, and it would take 1h
We can, but that one also can't be all-or-nothing without taking two
steps -- so two hours. If that `deployAtEnd` was working out it can be
all-or-nothing within the same Maven invocation, otherwise it has to
be two invocations (for all-or-nothing). Insert picture of sad puppy
here.
> And then have this pipeline that does the testing.
>
> If we only build SNAPSHOT after a 100% successfull complete pipeline
> with all testing etc. Then it may delay and take days/weeks.
> There can be odd / weird test failures once in a while. So I would
> like to separate them, and have up-to-date SNAPSHOTs
>
> If we have 1 pipeline then I am okay with the deploy in the build
> phase, so a SNAPSHOT is up-to-date.
I think it's probably best to have a single pipeline and a `Build &
Deploy` stage. Let me make that change.
zoran
--
Zoran Regvart
Re: Jenkins Pipeline Build Missing Deploy Phase?
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
Can we have another pipeline that just does the deploy?
Then we can have the deploy to run once per day.
And if we are in need of a quicker SNAPSHOT we can kick the job
manually, and it would take 1h
And then have this pipeline that does the testing.
If we only build SNAPSHOT after a 100% successfull complete pipeline
with all testing etc. Then it may delay and take days/weeks.
There can be odd / weird test failures once in a while. So I would
like to separate them, and have up-to-date SNAPSHOTs
If we have 1 pipeline then I am okay with the deploy in the build
phase, so a SNAPSHOT is up-to-date.
On Wed, Mar 21, 2018 at 7:48 AM, Zoran Regvart <zo...@regvart.com> wrote:
> Hi Pascal & Cameleers,
> well, seems that I have found a way to deploy to the ASF Maven
> repository, it adds another 1h to the build though.
>
> The change[1] is on `test-jenkinsfile` branch and it restores the
> `Deploy` stage right after the `Build` stage, this is similar to the
> way we had *-notest builds that deployed before pipeline.
>
> Because we're now using Jenkins pipeline[2] and not the Maven plugin
> to make the deploy all-or-nothing we need to do this in Maven two
> invocations as `deployAtEnd` for `maven-deploy-plugin` didn't seem to
> do the trick.
>
> So the question is, are we OK with adding another hour to the build or
> should we loose the all-or-nothing deploy and deploy in the `Build`
> stage?
>
> zoran
>
> [1] https://gitbox.apache.org/repos/asf?p=camel.git;a=commitdiff;h=5e32e07b88536712ec67861cfc289a40c7ee703c
> [2] https://builds.apache.org/view/A-D/view/Camel/job/Camel/job/test-jenkinsfile/
>
> On Tue, Mar 20, 2018 at 9:54 AM, Zoran Regvart <zo...@regvart.com> wrote:
>> Hi Pascal,
>> yeah, I think the latest commit will fix this[1]. Not sure why just
>> invoking the deploy phase didn't.
>>
>> zoran
>>
>> [1] https://gitbox.apache.org/repos/asf?p=camel.git;a=commitdiff;h=91e51260d57944dd377284961b3f28781679225e
>>
>> On Mon, Mar 19, 2018 at 9:58 PM, Pascal Schumacher
>> <pa...@gmx.net> wrote:
>>> Hi Zoran,
>>>
>>> thanks for looking into this!
>>>
>>> The last build was successful, but nothing was deployed.
>>>
>>> I guess we are affected by "MDEPLOY-193: deployAtEnd does not deploy
>>> artifacts for multi-module project with build extensions"
>>> https://issues.apache.org/jira/browse/MDEPLOY-193 (or
>>> https://issues.apache.org/jira/browse/MDEPLOY-226 or
>>> https://issues.apache.org/jira/browse/MDEPLOY-201). :(
>>>
>>> - Pascal
>>>
>>>
>>> Am 19.03.2018 um 08:58 schrieb Zoran Regvart:
>>>>
>>>> Hello,
>>>> no luck, the build failed on `bom-generator-maven-plugin` because no
>>>> Maven artefact was attached for that module in Maven reactor. I've
>>>> replaced the `install` goal in `Build` stage with `deploy` as at that
>>>> point the Maven reactor is populated.
>>>> Previously deploying to ASF Maven repository was done by Jenkins Maven
>>>> plugin which kept track of all produced artefacts so it can be
>>>> performed separately from the main Maven build. With pipeline that is
>>>> no longer possible.
>>>> I've added `deployAtEnd` flag so we deploy to the repository only if
>>>> the build passes. This doesn't mean that the -SNAPSHOT artefacts in
>>>> pass code checks or unit/integration tests, but that's how it used to
>>>> work with in the previous job constalation[1].
>>>>
>>>> zoran
>>>>
>>>> [1] https://builds.apache.org/view/C/view/Apache
>>>> Camel/job/Camel.trunk.notest/
>>>>
>>>> On Sun, Mar 18, 2018 at 9:23 PM, Zoran Regvart <zo...@regvart.com> wrote:
>>>>>
>>>>> Hi Pascal,
>>>>> good catch! The `Deploy` stage was using `install` phase whereas it
>>>>> should invoke the maven-deploy-plugin (i.e. `deploy:deploy`). Let's
>>>>> see if artifacts get deployed in pipeline build 140[1].
>>>>>
>>>>> I've also configured 4h polling period, seems that master wasn't built
>>>>> from 15th, I'm not 100% sure if this is an issue with gitpubsub[2] or
>>>>> with the way the job is configured. From what I understand Jenkins
>>>>> should be notified of any change to any ASF git repository.
>>>>>
>>>>> zoran
>>>>>
>>>>> [1]
>>>>> https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel/job/master/140/
>>>>> [2] https://www.apache.org/dev/gitpubsub.html
>>>>>
>>>>> On Sun, Mar 18, 2018 at 12:42 PM, Pascal Schumacher
>>>>> <pa...@gmx.net> wrote:
>>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> Jenkins successfully build camel a few hours ago, but when I try to
>>>>>> build
>>>>>> only camel-core locally I get:
>>>>>>
>>>>>> [INFO] Building Camel :: Core 2.22.0-SNAPSHOT
>>>>>> [INFO] --------------------------------[ jar
>>>>>> ]---------------------------------
>>>>>> Downloading from apache.snapshots:
>>>>>>
>>>>>> http://repository.apache.org/snapshots/org/apache/camel/camel-package-maven-plugin/2.22.0-SNAPSHOT/maven-metadata.xml
>>>>>> Downloading from apache.snapshots:
>>>>>>
>>>>>> http://repository.apache.org/snapshots/org/apache/camel/camel-package-maven-plugin/2.22.0-SNAPSHOT/camel-package-maven-plugin-2.22.0-SNAPSHOT.pom
>>>>>> [WARNING] The POM for
>>>>>> org.apache.camel:camel-package-maven-plugin:jar:2.22.0-SNAPSHOT is
>>>>>> missing,
>>>>>> no dependency information available
>>>>>> Downloading from apache.snapshots:
>>>>>>
>>>>>> http://repository.apache.org/snapshots/org/apache/camel/camel-package-maven-plugin/2.22.0-SNAPSHOT/camel-package-maven-plugin-2.22.0-SNAPSHOT.jar
>>>>>>
>>>>>> [ERROR] Plugin
>>>>>> org.apache.camel:camel-package-maven-plugin:2.22.0-SNAPSHOT
>>>>>> or one of its dependencies could not be resolved: Could not find
>>>>>> artifact
>>>>>> org.apache.camel:camel-package-maven-plugin:jar:2.22.0-SNAPSHOT in
>>>>>> apache.snapshots (http://repository.apache.org/snapshots/) -> [Help 1]
>>>>>>
>>>>>>
>>>>>> https://repository.apache.org/content/groups/snapshots/org/apache/camel/apache-camel/
>>>>>> does not contains 2.22.0-SNAPSHOT and the build output of
>>>>>>
>>>>>> https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel/job/master/139/console
>>>>>> does not contain any maven-deploy-plugin output.
>>>>>>
>>>>>> So I guess the Jenkins pipeline build is missing the deploy phase, or
>>>>>> are
>>>>>> camel-snapshot supposed to be deployed my some other means?
>>>>>>
>>>>>> Cheers,
>>>>>>
>>>>>> Pascal
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Zoran Regvart
>>>>
>>>>
>>>>
>>>
>>
>>
>>
>> --
>> Zoran Regvart
>
>
>
> --
> Zoran Regvart
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Re: Jenkins Pipeline Build Missing Deploy Phase?
Posted by Zoran Regvart <zo...@regvart.com>.
Hi Pascal & Cameleers,
well, seems that I have found a way to deploy to the ASF Maven
repository, it adds another 1h to the build though.
The change[1] is on `test-jenkinsfile` branch and it restores the
`Deploy` stage right after the `Build` stage, this is similar to the
way we had *-notest builds that deployed before pipeline.
Because we're now using Jenkins pipeline[2] and not the Maven plugin
to make the deploy all-or-nothing we need to do this in Maven two
invocations as `deployAtEnd` for `maven-deploy-plugin` didn't seem to
do the trick.
So the question is, are we OK with adding another hour to the build or
should we loose the all-or-nothing deploy and deploy in the `Build`
stage?
zoran
[1] https://gitbox.apache.org/repos/asf?p=camel.git;a=commitdiff;h=5e32e07b88536712ec67861cfc289a40c7ee703c
[2] https://builds.apache.org/view/A-D/view/Camel/job/Camel/job/test-jenkinsfile/
On Tue, Mar 20, 2018 at 9:54 AM, Zoran Regvart <zo...@regvart.com> wrote:
> Hi Pascal,
> yeah, I think the latest commit will fix this[1]. Not sure why just
> invoking the deploy phase didn't.
>
> zoran
>
> [1] https://gitbox.apache.org/repos/asf?p=camel.git;a=commitdiff;h=91e51260d57944dd377284961b3f28781679225e
>
> On Mon, Mar 19, 2018 at 9:58 PM, Pascal Schumacher
> <pa...@gmx.net> wrote:
>> Hi Zoran,
>>
>> thanks for looking into this!
>>
>> The last build was successful, but nothing was deployed.
>>
>> I guess we are affected by "MDEPLOY-193: deployAtEnd does not deploy
>> artifacts for multi-module project with build extensions"
>> https://issues.apache.org/jira/browse/MDEPLOY-193 (or
>> https://issues.apache.org/jira/browse/MDEPLOY-226 or
>> https://issues.apache.org/jira/browse/MDEPLOY-201). :(
>>
>> - Pascal
>>
>>
>> Am 19.03.2018 um 08:58 schrieb Zoran Regvart:
>>>
>>> Hello,
>>> no luck, the build failed on `bom-generator-maven-plugin` because no
>>> Maven artefact was attached for that module in Maven reactor. I've
>>> replaced the `install` goal in `Build` stage with `deploy` as at that
>>> point the Maven reactor is populated.
>>> Previously deploying to ASF Maven repository was done by Jenkins Maven
>>> plugin which kept track of all produced artefacts so it can be
>>> performed separately from the main Maven build. With pipeline that is
>>> no longer possible.
>>> I've added `deployAtEnd` flag so we deploy to the repository only if
>>> the build passes. This doesn't mean that the -SNAPSHOT artefacts in
>>> pass code checks or unit/integration tests, but that's how it used to
>>> work with in the previous job constalation[1].
>>>
>>> zoran
>>>
>>> [1] https://builds.apache.org/view/C/view/Apache
>>> Camel/job/Camel.trunk.notest/
>>>
>>> On Sun, Mar 18, 2018 at 9:23 PM, Zoran Regvart <zo...@regvart.com> wrote:
>>>>
>>>> Hi Pascal,
>>>> good catch! The `Deploy` stage was using `install` phase whereas it
>>>> should invoke the maven-deploy-plugin (i.e. `deploy:deploy`). Let's
>>>> see if artifacts get deployed in pipeline build 140[1].
>>>>
>>>> I've also configured 4h polling period, seems that master wasn't built
>>>> from 15th, I'm not 100% sure if this is an issue with gitpubsub[2] or
>>>> with the way the job is configured. From what I understand Jenkins
>>>> should be notified of any change to any ASF git repository.
>>>>
>>>> zoran
>>>>
>>>> [1]
>>>> https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel/job/master/140/
>>>> [2] https://www.apache.org/dev/gitpubsub.html
>>>>
>>>> On Sun, Mar 18, 2018 at 12:42 PM, Pascal Schumacher
>>>> <pa...@gmx.net> wrote:
>>>>>
>>>>> Hello,
>>>>>
>>>>> Jenkins successfully build camel a few hours ago, but when I try to
>>>>> build
>>>>> only camel-core locally I get:
>>>>>
>>>>> [INFO] Building Camel :: Core 2.22.0-SNAPSHOT
>>>>> [INFO] --------------------------------[ jar
>>>>> ]---------------------------------
>>>>> Downloading from apache.snapshots:
>>>>>
>>>>> http://repository.apache.org/snapshots/org/apache/camel/camel-package-maven-plugin/2.22.0-SNAPSHOT/maven-metadata.xml
>>>>> Downloading from apache.snapshots:
>>>>>
>>>>> http://repository.apache.org/snapshots/org/apache/camel/camel-package-maven-plugin/2.22.0-SNAPSHOT/camel-package-maven-plugin-2.22.0-SNAPSHOT.pom
>>>>> [WARNING] The POM for
>>>>> org.apache.camel:camel-package-maven-plugin:jar:2.22.0-SNAPSHOT is
>>>>> missing,
>>>>> no dependency information available
>>>>> Downloading from apache.snapshots:
>>>>>
>>>>> http://repository.apache.org/snapshots/org/apache/camel/camel-package-maven-plugin/2.22.0-SNAPSHOT/camel-package-maven-plugin-2.22.0-SNAPSHOT.jar
>>>>>
>>>>> [ERROR] Plugin
>>>>> org.apache.camel:camel-package-maven-plugin:2.22.0-SNAPSHOT
>>>>> or one of its dependencies could not be resolved: Could not find
>>>>> artifact
>>>>> org.apache.camel:camel-package-maven-plugin:jar:2.22.0-SNAPSHOT in
>>>>> apache.snapshots (http://repository.apache.org/snapshots/) -> [Help 1]
>>>>>
>>>>>
>>>>> https://repository.apache.org/content/groups/snapshots/org/apache/camel/apache-camel/
>>>>> does not contains 2.22.0-SNAPSHOT and the build output of
>>>>>
>>>>> https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel/job/master/139/console
>>>>> does not contain any maven-deploy-plugin output.
>>>>>
>>>>> So I guess the Jenkins pipeline build is missing the deploy phase, or
>>>>> are
>>>>> camel-snapshot supposed to be deployed my some other means?
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Pascal
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Zoran Regvart
>>>
>>>
>>>
>>
>
>
>
> --
> Zoran Regvart
--
Zoran Regvart
Re: Jenkins Pipeline Build Missing Deploy Phase?
Posted by Zoran Regvart <zo...@regvart.com>.
Hi Pascal,
yeah, I think the latest commit will fix this[1]. Not sure why just
invoking the deploy phase didn't.
zoran
[1] https://gitbox.apache.org/repos/asf?p=camel.git;a=commitdiff;h=91e51260d57944dd377284961b3f28781679225e
On Mon, Mar 19, 2018 at 9:58 PM, Pascal Schumacher
<pa...@gmx.net> wrote:
> Hi Zoran,
>
> thanks for looking into this!
>
> The last build was successful, but nothing was deployed.
>
> I guess we are affected by "MDEPLOY-193: deployAtEnd does not deploy
> artifacts for multi-module project with build extensions"
> https://issues.apache.org/jira/browse/MDEPLOY-193 (or
> https://issues.apache.org/jira/browse/MDEPLOY-226 or
> https://issues.apache.org/jira/browse/MDEPLOY-201). :(
>
> - Pascal
>
>
> Am 19.03.2018 um 08:58 schrieb Zoran Regvart:
>>
>> Hello,
>> no luck, the build failed on `bom-generator-maven-plugin` because no
>> Maven artefact was attached for that module in Maven reactor. I've
>> replaced the `install` goal in `Build` stage with `deploy` as at that
>> point the Maven reactor is populated.
>> Previously deploying to ASF Maven repository was done by Jenkins Maven
>> plugin which kept track of all produced artefacts so it can be
>> performed separately from the main Maven build. With pipeline that is
>> no longer possible.
>> I've added `deployAtEnd` flag so we deploy to the repository only if
>> the build passes. This doesn't mean that the -SNAPSHOT artefacts in
>> pass code checks or unit/integration tests, but that's how it used to
>> work with in the previous job constalation[1].
>>
>> zoran
>>
>> [1] https://builds.apache.org/view/C/view/Apache
>> Camel/job/Camel.trunk.notest/
>>
>> On Sun, Mar 18, 2018 at 9:23 PM, Zoran Regvart <zo...@regvart.com> wrote:
>>>
>>> Hi Pascal,
>>> good catch! The `Deploy` stage was using `install` phase whereas it
>>> should invoke the maven-deploy-plugin (i.e. `deploy:deploy`). Let's
>>> see if artifacts get deployed in pipeline build 140[1].
>>>
>>> I've also configured 4h polling period, seems that master wasn't built
>>> from 15th, I'm not 100% sure if this is an issue with gitpubsub[2] or
>>> with the way the job is configured. From what I understand Jenkins
>>> should be notified of any change to any ASF git repository.
>>>
>>> zoran
>>>
>>> [1]
>>> https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel/job/master/140/
>>> [2] https://www.apache.org/dev/gitpubsub.html
>>>
>>> On Sun, Mar 18, 2018 at 12:42 PM, Pascal Schumacher
>>> <pa...@gmx.net> wrote:
>>>>
>>>> Hello,
>>>>
>>>> Jenkins successfully build camel a few hours ago, but when I try to
>>>> build
>>>> only camel-core locally I get:
>>>>
>>>> [INFO] Building Camel :: Core 2.22.0-SNAPSHOT
>>>> [INFO] --------------------------------[ jar
>>>> ]---------------------------------
>>>> Downloading from apache.snapshots:
>>>>
>>>> http://repository.apache.org/snapshots/org/apache/camel/camel-package-maven-plugin/2.22.0-SNAPSHOT/maven-metadata.xml
>>>> Downloading from apache.snapshots:
>>>>
>>>> http://repository.apache.org/snapshots/org/apache/camel/camel-package-maven-plugin/2.22.0-SNAPSHOT/camel-package-maven-plugin-2.22.0-SNAPSHOT.pom
>>>> [WARNING] The POM for
>>>> org.apache.camel:camel-package-maven-plugin:jar:2.22.0-SNAPSHOT is
>>>> missing,
>>>> no dependency information available
>>>> Downloading from apache.snapshots:
>>>>
>>>> http://repository.apache.org/snapshots/org/apache/camel/camel-package-maven-plugin/2.22.0-SNAPSHOT/camel-package-maven-plugin-2.22.0-SNAPSHOT.jar
>>>>
>>>> [ERROR] Plugin
>>>> org.apache.camel:camel-package-maven-plugin:2.22.0-SNAPSHOT
>>>> or one of its dependencies could not be resolved: Could not find
>>>> artifact
>>>> org.apache.camel:camel-package-maven-plugin:jar:2.22.0-SNAPSHOT in
>>>> apache.snapshots (http://repository.apache.org/snapshots/) -> [Help 1]
>>>>
>>>>
>>>> https://repository.apache.org/content/groups/snapshots/org/apache/camel/apache-camel/
>>>> does not contains 2.22.0-SNAPSHOT and the build output of
>>>>
>>>> https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel/job/master/139/console
>>>> does not contain any maven-deploy-plugin output.
>>>>
>>>> So I guess the Jenkins pipeline build is missing the deploy phase, or
>>>> are
>>>> camel-snapshot supposed to be deployed my some other means?
>>>>
>>>> Cheers,
>>>>
>>>> Pascal
>>>>
>>>>
>>>
>>>
>>> --
>>> Zoran Regvart
>>
>>
>>
>
--
Zoran Regvart
Re: Jenkins Pipeline Build Missing Deploy Phase?
Posted by Pascal Schumacher <pa...@gmx.net>.
Hi Zoran,
thanks for looking into this!
The last build was successful, but nothing was deployed.
I guess we are affected by "MDEPLOY-193: deployAtEnd does not deploy
artifacts for multi-module project with build extensions"
https://issues.apache.org/jira/browse/MDEPLOY-193 (or
https://issues.apache.org/jira/browse/MDEPLOY-226 or
https://issues.apache.org/jira/browse/MDEPLOY-201). :(
- Pascal
Am 19.03.2018 um 08:58 schrieb Zoran Regvart:
> Hello,
> no luck, the build failed on `bom-generator-maven-plugin` because no
> Maven artefact was attached for that module in Maven reactor. I've
> replaced the `install` goal in `Build` stage with `deploy` as at that
> point the Maven reactor is populated.
> Previously deploying to ASF Maven repository was done by Jenkins Maven
> plugin which kept track of all produced artefacts so it can be
> performed separately from the main Maven build. With pipeline that is
> no longer possible.
> I've added `deployAtEnd` flag so we deploy to the repository only if
> the build passes. This doesn't mean that the -SNAPSHOT artefacts in
> pass code checks or unit/integration tests, but that's how it used to
> work with in the previous job constalation[1].
>
> zoran
>
> [1] https://builds.apache.org/view/C/view/Apache Camel/job/Camel.trunk.notest/
>
> On Sun, Mar 18, 2018 at 9:23 PM, Zoran Regvart <zo...@regvart.com> wrote:
>> Hi Pascal,
>> good catch! The `Deploy` stage was using `install` phase whereas it
>> should invoke the maven-deploy-plugin (i.e. `deploy:deploy`). Let's
>> see if artifacts get deployed in pipeline build 140[1].
>>
>> I've also configured 4h polling period, seems that master wasn't built
>> from 15th, I'm not 100% sure if this is an issue with gitpubsub[2] or
>> with the way the job is configured. From what I understand Jenkins
>> should be notified of any change to any ASF git repository.
>>
>> zoran
>>
>> [1] https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel/job/master/140/
>> [2] https://www.apache.org/dev/gitpubsub.html
>>
>> On Sun, Mar 18, 2018 at 12:42 PM, Pascal Schumacher
>> <pa...@gmx.net> wrote:
>>> Hello,
>>>
>>> Jenkins successfully build camel a few hours ago, but when I try to build
>>> only camel-core locally I get:
>>>
>>> [INFO] Building Camel :: Core 2.22.0-SNAPSHOT
>>> [INFO] --------------------------------[ jar
>>> ]---------------------------------
>>> Downloading from apache.snapshots:
>>> http://repository.apache.org/snapshots/org/apache/camel/camel-package-maven-plugin/2.22.0-SNAPSHOT/maven-metadata.xml
>>> Downloading from apache.snapshots:
>>> http://repository.apache.org/snapshots/org/apache/camel/camel-package-maven-plugin/2.22.0-SNAPSHOT/camel-package-maven-plugin-2.22.0-SNAPSHOT.pom
>>> [WARNING] The POM for
>>> org.apache.camel:camel-package-maven-plugin:jar:2.22.0-SNAPSHOT is missing,
>>> no dependency information available
>>> Downloading from apache.snapshots:
>>> http://repository.apache.org/snapshots/org/apache/camel/camel-package-maven-plugin/2.22.0-SNAPSHOT/camel-package-maven-plugin-2.22.0-SNAPSHOT.jar
>>>
>>> [ERROR] Plugin org.apache.camel:camel-package-maven-plugin:2.22.0-SNAPSHOT
>>> or one of its dependencies could not be resolved: Could not find artifact
>>> org.apache.camel:camel-package-maven-plugin:jar:2.22.0-SNAPSHOT in
>>> apache.snapshots (http://repository.apache.org/snapshots/) -> [Help 1]
>>>
>>> https://repository.apache.org/content/groups/snapshots/org/apache/camel/apache-camel/
>>> does not contains 2.22.0-SNAPSHOT and the build output of
>>> https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel/job/master/139/console
>>> does not contain any maven-deploy-plugin output.
>>>
>>> So I guess the Jenkins pipeline build is missing the deploy phase, or are
>>> camel-snapshot supposed to be deployed my some other means?
>>>
>>> Cheers,
>>>
>>> Pascal
>>>
>>>
>>
>>
>> --
>> Zoran Regvart
>
>
Re: Jenkins Pipeline Build Missing Deploy Phase?
Posted by Zoran Regvart <zo...@regvart.com>.
Hello,
no luck, the build failed on `bom-generator-maven-plugin` because no
Maven artefact was attached for that module in Maven reactor. I've
replaced the `install` goal in `Build` stage with `deploy` as at that
point the Maven reactor is populated.
Previously deploying to ASF Maven repository was done by Jenkins Maven
plugin which kept track of all produced artefacts so it can be
performed separately from the main Maven build. With pipeline that is
no longer possible.
I've added `deployAtEnd` flag so we deploy to the repository only if
the build passes. This doesn't mean that the -SNAPSHOT artefacts in
pass code checks or unit/integration tests, but that's how it used to
work with in the previous job constalation[1].
zoran
[1] https://builds.apache.org/view/C/view/Apache Camel/job/Camel.trunk.notest/
On Sun, Mar 18, 2018 at 9:23 PM, Zoran Regvart <zo...@regvart.com> wrote:
> Hi Pascal,
> good catch! The `Deploy` stage was using `install` phase whereas it
> should invoke the maven-deploy-plugin (i.e. `deploy:deploy`). Let's
> see if artifacts get deployed in pipeline build 140[1].
>
> I've also configured 4h polling period, seems that master wasn't built
> from 15th, I'm not 100% sure if this is an issue with gitpubsub[2] or
> with the way the job is configured. From what I understand Jenkins
> should be notified of any change to any ASF git repository.
>
> zoran
>
> [1] https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel/job/master/140/
> [2] https://www.apache.org/dev/gitpubsub.html
>
> On Sun, Mar 18, 2018 at 12:42 PM, Pascal Schumacher
> <pa...@gmx.net> wrote:
>> Hello,
>>
>> Jenkins successfully build camel a few hours ago, but when I try to build
>> only camel-core locally I get:
>>
>> [INFO] Building Camel :: Core 2.22.0-SNAPSHOT
>> [INFO] --------------------------------[ jar
>> ]---------------------------------
>> Downloading from apache.snapshots:
>> http://repository.apache.org/snapshots/org/apache/camel/camel-package-maven-plugin/2.22.0-SNAPSHOT/maven-metadata.xml
>> Downloading from apache.snapshots:
>> http://repository.apache.org/snapshots/org/apache/camel/camel-package-maven-plugin/2.22.0-SNAPSHOT/camel-package-maven-plugin-2.22.0-SNAPSHOT.pom
>> [WARNING] The POM for
>> org.apache.camel:camel-package-maven-plugin:jar:2.22.0-SNAPSHOT is missing,
>> no dependency information available
>> Downloading from apache.snapshots:
>> http://repository.apache.org/snapshots/org/apache/camel/camel-package-maven-plugin/2.22.0-SNAPSHOT/camel-package-maven-plugin-2.22.0-SNAPSHOT.jar
>>
>> [ERROR] Plugin org.apache.camel:camel-package-maven-plugin:2.22.0-SNAPSHOT
>> or one of its dependencies could not be resolved: Could not find artifact
>> org.apache.camel:camel-package-maven-plugin:jar:2.22.0-SNAPSHOT in
>> apache.snapshots (http://repository.apache.org/snapshots/) -> [Help 1]
>>
>> https://repository.apache.org/content/groups/snapshots/org/apache/camel/apache-camel/
>> does not contains 2.22.0-SNAPSHOT and the build output of
>> https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel/job/master/139/console
>> does not contain any maven-deploy-plugin output.
>>
>> So I guess the Jenkins pipeline build is missing the deploy phase, or are
>> camel-snapshot supposed to be deployed my some other means?
>>
>> Cheers,
>>
>> Pascal
>>
>>
>
>
>
> --
> Zoran Regvart
--
Zoran Regvart
Re: Jenkins Pipeline Build Missing Deploy Phase?
Posted by Zoran Regvart <zo...@regvart.com>.
Hi Pascal,
good catch! The `Deploy` stage was using `install` phase whereas it
should invoke the maven-deploy-plugin (i.e. `deploy:deploy`). Let's
see if artifacts get deployed in pipeline build 140[1].
I've also configured 4h polling period, seems that master wasn't built
from 15th, I'm not 100% sure if this is an issue with gitpubsub[2] or
with the way the job is configured. From what I understand Jenkins
should be notified of any change to any ASF git repository.
zoran
[1] https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel/job/master/140/
[2] https://www.apache.org/dev/gitpubsub.html
On Sun, Mar 18, 2018 at 12:42 PM, Pascal Schumacher
<pa...@gmx.net> wrote:
> Hello,
>
> Jenkins successfully build camel a few hours ago, but when I try to build
> only camel-core locally I get:
>
> [INFO] Building Camel :: Core 2.22.0-SNAPSHOT
> [INFO] --------------------------------[ jar
> ]---------------------------------
> Downloading from apache.snapshots:
> http://repository.apache.org/snapshots/org/apache/camel/camel-package-maven-plugin/2.22.0-SNAPSHOT/maven-metadata.xml
> Downloading from apache.snapshots:
> http://repository.apache.org/snapshots/org/apache/camel/camel-package-maven-plugin/2.22.0-SNAPSHOT/camel-package-maven-plugin-2.22.0-SNAPSHOT.pom
> [WARNING] The POM for
> org.apache.camel:camel-package-maven-plugin:jar:2.22.0-SNAPSHOT is missing,
> no dependency information available
> Downloading from apache.snapshots:
> http://repository.apache.org/snapshots/org/apache/camel/camel-package-maven-plugin/2.22.0-SNAPSHOT/camel-package-maven-plugin-2.22.0-SNAPSHOT.jar
>
> [ERROR] Plugin org.apache.camel:camel-package-maven-plugin:2.22.0-SNAPSHOT
> or one of its dependencies could not be resolved: Could not find artifact
> org.apache.camel:camel-package-maven-plugin:jar:2.22.0-SNAPSHOT in
> apache.snapshots (http://repository.apache.org/snapshots/) -> [Help 1]
>
> https://repository.apache.org/content/groups/snapshots/org/apache/camel/apache-camel/
> does not contains 2.22.0-SNAPSHOT and the build output of
> https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel/job/master/139/console
> does not contain any maven-deploy-plugin output.
>
> So I guess the Jenkins pipeline build is missing the deploy phase, or are
> camel-snapshot supposed to be deployed my some other means?
>
> Cheers,
>
> Pascal
>
>
--
Zoran Regvart