[JBoss JIRA] (JBIDE-21662) Server adapter: workspace project is not automatically published if there was no initial publish
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-21662:
-------------------------------------
Summary: Server adapter: workspace project is not automatically published if there was no initial publish
Key: JBIDE-21662
URL: https://issues.jboss.org/browse/JBIDE-21662
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.CR1
Reporter: Marián Labuda
When I am having a workspace project, OS3 application and server adapter, application should be automatically changed based on local file disk changes as it was introduced in JBIDE-21371. But auto-publish does not work if there was not performed initial publish on server adapter which links workspace project with OS 3 application.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21657) set up jobs to handle building from PRs
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21657?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-21657 at 2/8/16 4:44 AM:
------------------------------------------------------------
Another limitation I just realized is that the PR builder needs to be more selective -- jobs set to build from master should only build from that branch or from master-based PRs, or else deps will come from the wrong parent pom, component versions, and TP. Witness:
{code}
[INFO] Adding repository http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5...
[INFO] Fetching content.jar from http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... (0B of 668.79kB at 0B/s)
[INFO] Adding repository http://download.jboss.org/jbosstools/updates/nightly/core/master
[INFO] Resolving dependencies of MavenProject: org.jboss.tools:org.jboss.tools.site.central.earlyaccess:4.3.1-SNAPSHOT @ /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.child-sites__pull-request_master/jdk/jdk1.8/label_exp/(RHEL6||RHEL7||beaker||jboss-prod)&&!ia64&&!ppc64&&!rhts/projectName/earlyaccess/sources/aggregate/earlyaccess-site/pom.xml
[INFO] {osgi.os=macosx, osgi.ws=cocoa, org.eclipse.update.install.features=true, osgi.arch=x86_64}
[ERROR] Cannot resolve project dependencies:
[ERROR] Software being installed: org.jboss.tools.site.central.earlyaccess raw:4.3.1.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):4.3.1-SNAPSHOT
[ERROR] Missing requirement: org.jboss.tools.foundation.ui 1.3.0.Alpha1-v20160126-2136-B879 requires 'bundle org.eclipse.ui.forms 3.7.0' but it could not be found
[ERROR] Cannot satisfy dependency: org.jboss.ide.eclipse.as.ui 3.2.0.Alpha1-v20160203-2109-B913 depends on: bundle org.jboss.tools.foundation.ui 1.1.0
[ERROR] Cannot satisfy dependency: org.jboss.tools.arquillian.feature.feature.group 1.2.100.Alpha1-v20151213-0942-B361 depends on: org.jboss.tools.arquillian.ui [1.2.100.Alpha1-v20151213-0942-B361]
[ERROR] Cannot satisfy dependency: org.jboss.tools.arquillian.ui 1.2.100.Alpha1-v20151213-0942-B361 depends on: bundle org.jboss.ide.eclipse.as.ui 2.4.0
[ERROR] Cannot satisfy dependency: org.jboss.tools.site.central.earlyaccess raw:4.3.1.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):4.3.1-SNAPSHOT depends on: org.jboss.tools.arquillian.feature.feature.group 0.0.0
{code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-site...
So need something like a filter/check for https://api.github.com/repos/jbosstools/jbosstools-build-sites/pulls?stat... vs. https://api.github.com/repos/jbosstools/jbosstools-build-sites/pulls?stat...
was (Author: nickboldt):
Another limitation I just realized is that the PR builder needs to be more selective -- jobs set to build from master should only build from that branch or from master-based PRs, or else deps will come from the wrong parent pom, component versions, and TP. Witness:
{code}
[INFO] Adding repository http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5...
[INFO] Fetching content.jar from http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... (0B of 668.79kB at 0B/s)
[INFO] Adding repository http://download.jboss.org/jbosstools/updates/nightly/core/master
[INFO] Resolving dependencies of MavenProject: org.jboss.tools:org.jboss.tools.site.central.earlyaccess:4.3.1-SNAPSHOT @ /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.child-sites__pull-request_master/jdk/jdk1.8/label_exp/(RHEL6||RHEL7||beaker||jboss-prod)&&!ia64&&!ppc64&&!rhts/projectName/earlyaccess/sources/aggregate/earlyaccess-site/pom.xml
[INFO] {osgi.os=macosx, osgi.ws=cocoa, org.eclipse.update.install.features=true, osgi.arch=x86_64}
[ERROR] Cannot resolve project dependencies:
[ERROR] Software being installed: org.jboss.tools.site.central.earlyaccess raw:4.3.1.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):4.3.1-SNAPSHOT
[ERROR] Missing requirement: org.jboss.tools.foundation.ui 1.3.0.Alpha1-v20160126-2136-B879 requires 'bundle org.eclipse.ui.forms 3.7.0' but it could not be found
[ERROR] Cannot satisfy dependency: org.jboss.ide.eclipse.as.ui 3.2.0.Alpha1-v20160203-2109-B913 depends on: bundle org.jboss.tools.foundation.ui 1.1.0
[ERROR] Cannot satisfy dependency: org.jboss.tools.arquillian.feature.feature.group 1.2.100.Alpha1-v20151213-0942-B361 depends on: org.jboss.tools.arquillian.ui [1.2.100.Alpha1-v20151213-0942-B361]
[ERROR] Cannot satisfy dependency: org.jboss.tools.arquillian.ui 1.2.100.Alpha1-v20151213-0942-B361 depends on: bundle org.jboss.ide.eclipse.as.ui 2.4.0
[ERROR] Cannot satisfy dependency: org.jboss.tools.site.central.earlyaccess raw:4.3.1.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):4.3.1-SNAPSHOT depends on: org.jboss.tools.arquillian.feature.feature.group 0.0.0
{code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-site...
> set up jobs to handle building from PRs
> ---------------------------------------
>
> Key: JBIDE-21657
> URL: https://issues.jboss.org/browse/JBIDE-21657
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.1.Beta2, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
>
> First experimental build:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit...
> Output:
> http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui...
> {code}
> "revision" : {
> "HEAD" : "bfe76fb3f3c34d68b873d0acf715e2145e4cb805",
> "currentBranch" : "HEAD",
> "knownReferences" : [{
> "name" : "origin",
> "url" : "git://github.com/jbosstools/jbosstools-build-sites.git",
> "ref" : "pr/221/merge"
> }]
> },
> {code}
> http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui...
> {code}
> #Fri Feb 05 16:42:42 EST 2016
> null\:merge=bfe76fb3f3c34d68b873d0acf715e2145e4cb805
> HEAD=bfe76fb3f3c34d68b873d0acf715e2145e4cb805
> {code}
> build log:
> {code}
> Started by upstream project "jbosstools-build-sites.aggregate.child-sites__pull-request_master" build number 1
> originally caused by:
> GitHub pull request #221 of commit 50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge conflicts.
> ...
> Fetching upstream changes from git://github.com/jbosstools/jbosstools-build-sites.git
> > git -c core.askpass=true fetch --tags --progress git://github.com/jbosstools/jbosstools-build-sites.git +refs/heads/*:refs/remotes/origin/* +refs/pull/*:refs/remotes/origin/pr/*
> Checking out Revision bfe76fb3f3c34d68b873d0acf715e2145e4cb805 (refs/remotes/origin/pr/221/merge)
> > git config core.sparsecheckout # timeout=10
> > git checkout -f bfe76fb3f3c34d68b873d0acf715e2145e4cb805
> {code}
> vars:
> {code}
> -DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d
> -DghprbPullId=221
> -Dsha1=origin/pr/221/merge
> "-DghprbPullDescription=GitHub pull request #221 of commit 50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge conflicts."
> -DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21371) Server Adapter: implement automatic publishing
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21371?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-21371:
----------------------------------------
Ok. It looks like a bug to me if you have to publish the app manually at the very first time after os server adapter creation. But we can report it as a separate issue and close this one.
> Server Adapter: implement automatic publishing
> ----------------------------------------------
>
> Key: JBIDE-21371
> URL: https://issues.jboss.org/browse/JBIDE-21371
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Labels: new_and_noteworthy, openshift_v3, server_adapter
> Fix For: 4.3.1.Beta2
>
>
> Currently the OpenShift 3 server adapter is only publishing when you manually triggering it to do so. We should now have fully automatic publishing that happens whenever the project that it is bound to changes on disk.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21657) set up jobs to handle building from PRs
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21657?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-21657:
------------------------------------
with PR 224 applied, we can publish a PR into /pulls/ and it'll look like this:
http://download.jboss.org/jbosstools/neon/snapshots/pulls/jbosstools-buil...
> set up jobs to handle building from PRs
> ---------------------------------------
>
> Key: JBIDE-21657
> URL: https://issues.jboss.org/browse/JBIDE-21657
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.1.Beta2, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
>
> First experimental build:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit...
> Output:
> http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui...
> {code}
> "revision" : {
> "HEAD" : "bfe76fb3f3c34d68b873d0acf715e2145e4cb805",
> "currentBranch" : "HEAD",
> "knownReferences" : [{
> "name" : "origin",
> "url" : "git://github.com/jbosstools/jbosstools-build-sites.git",
> "ref" : "pr/221/merge"
> }]
> },
> {code}
> http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui...
> {code}
> #Fri Feb 05 16:42:42 EST 2016
> null\:merge=bfe76fb3f3c34d68b873d0acf715e2145e4cb805
> HEAD=bfe76fb3f3c34d68b873d0acf715e2145e4cb805
> {code}
> build log:
> {code}
> Started by upstream project "jbosstools-build-sites.aggregate.child-sites__pull-request_master" build number 1
> originally caused by:
> GitHub pull request #221 of commit 50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge conflicts.
> ...
> Fetching upstream changes from git://github.com/jbosstools/jbosstools-build-sites.git
> > git -c core.askpass=true fetch --tags --progress git://github.com/jbosstools/jbosstools-build-sites.git +refs/heads/*:refs/remotes/origin/* +refs/pull/*:refs/remotes/origin/pr/*
> Checking out Revision bfe76fb3f3c34d68b873d0acf715e2145e4cb805 (refs/remotes/origin/pr/221/merge)
> > git config core.sparsecheckout # timeout=10
> > git checkout -f bfe76fb3f3c34d68b873d0acf715e2145e4cb805
> {code}
> vars:
> {code}
> -DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d
> -DghprbPullId=221
> -Dsha1=origin/pr/221/merge
> "-DghprbPullDescription=GitHub pull request #221 of commit 50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge conflicts."
> -DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (TOOLSDOC-705) JBDS 9.1 Beta2: Release Notes
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-705?page=com.atlassian.jira.plug... ]
Marián Labuda commented on TOOLSDOC-705:
----------------------------------------
It's missing a step of opening a New Server wizard. Because "From the Servers view" you cannot select "OpenShift 3 Server Adapter", you can select an existing server adapter or open a New Server wizard. So it should be either "From the New Server wizard, create a new Server by selecting ....". And/Or you could attach also information to open a New Server wizard from server view and then the latter. Is it more clear to you now?
> JBDS 9.1 Beta2: Release Notes
> -----------------------------
>
> Key: TOOLSDOC-705
> URL: https://issues.jboss.org/browse/TOOLSDOC-705
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Components: Release Notes
> Affects Versions: 9.1 Beta2
> Reporter: Misha Ali
> Assignee: Misha Ali
> Fix For: 9.1 Beta2
>
>
> Create new Beta2 release notes, fix the script and update the relevant details.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21657) set up jobs to handle building from PRs
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21657?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-21657 at 2/8/16 4:12 AM:
------------------------------------------------------------
Possible profile that would only publish to /pulls/ folder rather than /builds/ and /updates/ :
* https://github.com/jbosstools/jbosstools-build-sites/pull/223 (43x, incomplete)
* https://github.com/jbosstools/jbosstools-build-sites/pull/224 (master, more complete)
Then we need only tweak the jobs so they can do "if PR, run profile deploy-pr; else the usual check and deploy logic":
was (Author: nickboldt):
Possible profile that would only publish to /pulls/ folder rather than /builds/ and /updates/ :
https://github.com/jbosstools/jbosstools-build-sites/pull/223
Then we need only tweak the jobs so they can do "if PR, run profile deploy-pr; else the usual check and deploy logic":
> set up jobs to handle building from PRs
> ---------------------------------------
>
> Key: JBIDE-21657
> URL: https://issues.jboss.org/browse/JBIDE-21657
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.1.Beta2, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
>
> First experimental build:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit...
> Output:
> http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui...
> {code}
> "revision" : {
> "HEAD" : "bfe76fb3f3c34d68b873d0acf715e2145e4cb805",
> "currentBranch" : "HEAD",
> "knownReferences" : [{
> "name" : "origin",
> "url" : "git://github.com/jbosstools/jbosstools-build-sites.git",
> "ref" : "pr/221/merge"
> }]
> },
> {code}
> http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui...
> {code}
> #Fri Feb 05 16:42:42 EST 2016
> null\:merge=bfe76fb3f3c34d68b873d0acf715e2145e4cb805
> HEAD=bfe76fb3f3c34d68b873d0acf715e2145e4cb805
> {code}
> build log:
> {code}
> Started by upstream project "jbosstools-build-sites.aggregate.child-sites__pull-request_master" build number 1
> originally caused by:
> GitHub pull request #221 of commit 50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge conflicts.
> ...
> Fetching upstream changes from git://github.com/jbosstools/jbosstools-build-sites.git
> > git -c core.askpass=true fetch --tags --progress git://github.com/jbosstools/jbosstools-build-sites.git +refs/heads/*:refs/remotes/origin/* +refs/pull/*:refs/remotes/origin/pr/*
> Checking out Revision bfe76fb3f3c34d68b873d0acf715e2145e4cb805 (refs/remotes/origin/pr/221/merge)
> > git config core.sparsecheckout # timeout=10
> > git checkout -f bfe76fb3f3c34d68b873d0acf715e2145e4cb805
> {code}
> vars:
> {code}
> -DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d
> -DghprbPullId=221
> -Dsha1=origin/pr/221/merge
> "-DghprbPullDescription=GitHub pull request #221 of commit 50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge conflicts."
> -DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21657) set up jobs to handle building from PRs
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21657?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-21657:
------------------------------------
Another limitation I just realized is that the PR builder needs to be more selective -- jobs set to build from master should only build from that branch or from master-based PRs, or else deps will come from the wrong parent pom, component versions, and TP. Witness:
{code}
[INFO] Adding repository http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5...
[INFO] Fetching content.jar from http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... (0B of 668.79kB at 0B/s)
[INFO] Adding repository http://download.jboss.org/jbosstools/updates/nightly/core/master
[INFO] Resolving dependencies of MavenProject: org.jboss.tools:org.jboss.tools.site.central.earlyaccess:4.3.1-SNAPSHOT @ /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.child-sites__pull-request_master/jdk/jdk1.8/label_exp/(RHEL6||RHEL7||beaker||jboss-prod)&&!ia64&&!ppc64&&!rhts/projectName/earlyaccess/sources/aggregate/earlyaccess-site/pom.xml
[INFO] {osgi.os=macosx, osgi.ws=cocoa, org.eclipse.update.install.features=true, osgi.arch=x86_64}
[ERROR] Cannot resolve project dependencies:
[ERROR] Software being installed: org.jboss.tools.site.central.earlyaccess raw:4.3.1.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):4.3.1-SNAPSHOT
[ERROR] Missing requirement: org.jboss.tools.foundation.ui 1.3.0.Alpha1-v20160126-2136-B879 requires 'bundle org.eclipse.ui.forms 3.7.0' but it could not be found
[ERROR] Cannot satisfy dependency: org.jboss.ide.eclipse.as.ui 3.2.0.Alpha1-v20160203-2109-B913 depends on: bundle org.jboss.tools.foundation.ui 1.1.0
[ERROR] Cannot satisfy dependency: org.jboss.tools.arquillian.feature.feature.group 1.2.100.Alpha1-v20151213-0942-B361 depends on: org.jboss.tools.arquillian.ui [1.2.100.Alpha1-v20151213-0942-B361]
[ERROR] Cannot satisfy dependency: org.jboss.tools.arquillian.ui 1.2.100.Alpha1-v20151213-0942-B361 depends on: bundle org.jboss.ide.eclipse.as.ui 2.4.0
[ERROR] Cannot satisfy dependency: org.jboss.tools.site.central.earlyaccess raw:4.3.1.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):4.3.1-SNAPSHOT depends on: org.jboss.tools.arquillian.feature.feature.group 0.0.0
{code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-site...
> set up jobs to handle building from PRs
> ---------------------------------------
>
> Key: JBIDE-21657
> URL: https://issues.jboss.org/browse/JBIDE-21657
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.1.Beta2, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
>
> First experimental build:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit...
> Output:
> http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui...
> {code}
> "revision" : {
> "HEAD" : "bfe76fb3f3c34d68b873d0acf715e2145e4cb805",
> "currentBranch" : "HEAD",
> "knownReferences" : [{
> "name" : "origin",
> "url" : "git://github.com/jbosstools/jbosstools-build-sites.git",
> "ref" : "pr/221/merge"
> }]
> },
> {code}
> http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui...
> {code}
> #Fri Feb 05 16:42:42 EST 2016
> null\:merge=bfe76fb3f3c34d68b873d0acf715e2145e4cb805
> HEAD=bfe76fb3f3c34d68b873d0acf715e2145e4cb805
> {code}
> build log:
> {code}
> Started by upstream project "jbosstools-build-sites.aggregate.child-sites__pull-request_master" build number 1
> originally caused by:
> GitHub pull request #221 of commit 50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge conflicts.
> ...
> Fetching upstream changes from git://github.com/jbosstools/jbosstools-build-sites.git
> > git -c core.askpass=true fetch --tags --progress git://github.com/jbosstools/jbosstools-build-sites.git +refs/heads/*:refs/remotes/origin/* +refs/pull/*:refs/remotes/origin/pr/*
> Checking out Revision bfe76fb3f3c34d68b873d0acf715e2145e4cb805 (refs/remotes/origin/pr/221/merge)
> > git config core.sparsecheckout # timeout=10
> > git checkout -f bfe76fb3f3c34d68b873d0acf715e2145e4cb805
> {code}
> vars:
> {code}
> -DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d
> -DghprbPullId=221
> -Dsha1=origin/pr/221/merge
> "-DghprbPullDescription=GitHub pull request #221 of commit 50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge conflicts."
> -DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21371) Server Adapter: implement automatic publishing
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21371?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-21371:
---------------------------------------
I have not verified it back then, because it was not in our verification filters. Issues was probably closed by accident when NN label had been added. But to clarify it, I was experiencing auto-publishing behaviour in Beta2 respin-a. Once you have a new OS 3 application and you perform first Publish via a server adapter, every later change on disk is automatically published. Pure existence of server adapter and change on disk does not do magic without first publish.
> Server Adapter: implement automatic publishing
> ----------------------------------------------
>
> Key: JBIDE-21371
> URL: https://issues.jboss.org/browse/JBIDE-21371
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Labels: new_and_noteworthy, openshift_v3, server_adapter
> Fix For: 4.3.1.Beta2
>
>
> Currently the OpenShift 3 server adapter is only publishing when you manually triggering it to do so. We should now have fully automatic publishing that happens whenever the project that it is bound to changes on disk.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21657) set up jobs to handle building from PRs
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21657?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-21657:
------------------------------------
p2diff will simply show which features or plugins in a given project were changed by the PR. You could get the same information looking at the PR. Bear in mind too that each plugin will be shown as different because its Source-Reference in MANIFEST.MF will show a different SHA.
So, a p2diff would in fact show that ALL the features and plugins were different since they'd have different versions in their qualifier. And if we exclude versions from the p2diff, you'd only ever see when a NEW feature/plugin is added or a new dependency is included in the update site.
As to not keeping these things forever...
if I put everything into /snapshots/pulls/ then the automated cleanup scripts could be adjusted such that no more than 1 past pull request build would ever be retained, as we do currently for builds from the branch. Self-cleaning means you'd get to see your pull-request builds for a few days, but they'd disappear when they got sufficiently old.
> set up jobs to handle building from PRs
> ---------------------------------------
>
> Key: JBIDE-21657
> URL: https://issues.jboss.org/browse/JBIDE-21657
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.1.Beta2, 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
>
> First experimental build:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit...
> Output:
> http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui...
> {code}
> "revision" : {
> "HEAD" : "bfe76fb3f3c34d68b873d0acf715e2145e4cb805",
> "currentBranch" : "HEAD",
> "knownReferences" : [{
> "name" : "origin",
> "url" : "git://github.com/jbosstools/jbosstools-build-sites.git",
> "ref" : "pr/221/merge"
> }]
> },
> {code}
> http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui...
> {code}
> #Fri Feb 05 16:42:42 EST 2016
> null\:merge=bfe76fb3f3c34d68b873d0acf715e2145e4cb805
> HEAD=bfe76fb3f3c34d68b873d0acf715e2145e4cb805
> {code}
> build log:
> {code}
> Started by upstream project "jbosstools-build-sites.aggregate.child-sites__pull-request_master" build number 1
> originally caused by:
> GitHub pull request #221 of commit 50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge conflicts.
> ...
> Fetching upstream changes from git://github.com/jbosstools/jbosstools-build-sites.git
> > git -c core.askpass=true fetch --tags --progress git://github.com/jbosstools/jbosstools-build-sites.git +refs/heads/*:refs/remotes/origin/* +refs/pull/*:refs/remotes/origin/pr/*
> Checking out Revision bfe76fb3f3c34d68b873d0acf715e2145e4cb805 (refs/remotes/origin/pr/221/merge)
> > git config core.sparsecheckout # timeout=10
> > git checkout -f bfe76fb3f3c34d68b873d0acf715e2145e4cb805
> {code}
> vars:
> {code}
> -DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d
> -DghprbPullId=221
> -Dsha1=origin/pr/221/merge
> "-DghprbPullDescription=GitHub pull request #221 of commit 50c10ad83d250d2b86f5697c4581ba8f9cb4937d, no merge conflicts."
> -DghprbActualCommit=50c10ad83d250d2b86f5697c4581ba8f9cb4937d
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month