[JBoss JIRA] (JBIDE-22444) Client: release and use a final artifact of openshift-restclient-java
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22444?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22444:
-------------------------------------
Description: 4.4.0.Alpha2 is using openshift-restclient-java 4.0.4-SNAPSHOT. We should release a final version of the client and use it in the tooling (was: 4.4.0.Alpha2 is using openshift-restclient-java 4.0.4-SNAPSHOT. We should release a final version of the client and use it in the next milestone.)
> Client: release and use a final artifact of openshift-restclient-java
> ---------------------------------------------------------------------
>
> Key: JBIDE-22444
> URL: https://issues.jboss.org/browse/JBIDE-22444
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift
> Affects Versions: 4.4.0.Alpha3
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Blocker
> Fix For: 4.4.0.Alpha3
>
>
> 4.4.0.Alpha2 is using openshift-restclient-java 4.0.4-SNAPSHOT. We should release a final version of the client and use it in the tooling
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-21657) set up jobs to handle building from PRs
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21657?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-21657:
---------------------------------------------
since it is quite tedious to add user to everything I've started by creating a "bots" group, added "rhdevelopers-ci" and granted access to jbosstools/jbosstools-target-platforms.
Once you verify that works, I can go ahead and do the full dance.
ps. whoever owns rhdevelopers-ci needs to accept the invite.
> 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
> Priority: Critical
> Fix For: 4.4.0.Alpha3
>
>
> 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)
9 years, 10 months
[JBoss JIRA] (JBIDE-22454) Application Wizard: Build configuration wizard page has redundant environment variables table
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22454?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22454:
------------------------------------------
merged into master, thx!
> Application Wizard: Build configuration wizard page has redundant environment variables table
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-22454
> URL: https://issues.jboss.org/browse/JBIDE-22454
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha3
> Reporter: Marián Labuda
> Assignee: Jeff Cantrill
> Labels: application_wizard, openshift_v3
> Fix For: 4.4.0.Alpha3
>
> Attachments: screenshot-2.png, screenshot-3.png
>
>
> In New OpenShift Application wizard with selected builder image, there are 2 wizard pages containing same thing - table of environment variables passed to pod. First page is Build Configuration, where the table is empty. Second page is the immediately following one Deployment configuration and Scalability, where are environment variables even correctly prepared (obtained from image metadata). The first table, on Build configuration wizard page, should be removed, its redundant there.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22454) Application Wizard: Build configuration wizard page has redundant environment variables table
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22454?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-22454:
-------------------------------------
Fix Version/s: 4.4.0.Alpha3
(was: 4.4.x)
> Application Wizard: Build configuration wizard page has redundant environment variables table
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-22454
> URL: https://issues.jboss.org/browse/JBIDE-22454
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha3
> Reporter: Marián Labuda
> Assignee: Jeff Cantrill
> Labels: application_wizard, openshift_v3
> Fix For: 4.4.0.Alpha3
>
> Attachments: screenshot-2.png, screenshot-3.png
>
>
> In New OpenShift Application wizard with selected builder image, there are 2 wizard pages containing same thing - table of environment variables passed to pod. First page is Build Configuration, where the table is empty. Second page is the immediately following one Deployment configuration and Scalability, where are environment variables even correctly prepared (obtained from image metadata). The first table, on Build configuration wizard page, should be removed, its redundant there.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months