[JBoss JIRA] (JBIDE-24146) Support pipeline deployment style
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24146?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24146:
-------------------------------------
Sprint: devex #130 April 2017
> Support pipeline deployment style
> ---------------------------------
>
> Key: JBIDE-24146
> URL: https://issues.jboss.org/browse/JBIDE-24146
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.4.AM2
> Reporter: Jeff MAURY
> Assignee: Andre Dietisheim
> Labels: openshift, openshift_v3, wizard
> Fix For: 4.4.4.AM3
>
> Attachments: jenkins-pipeline-template.png, jenkins-variants.png, pipeline-build.png
>
>
> In the web-console jenkins pipelines are supported in the following way:
> * when opening up an empty project you get a special template:
> !jenkins-pipeline-template.png!
> * which offers 2 different jenkins variants (and a full example that contains app source and build pipeline):
> !jenkins-variants.png!
> * once executed you get a special build type *pipeline*
> !pipeline-build.png!
> * the full example template is using the following build config with the strategy type *JenkinsPipeline*:
> {code}
> apiVersion: v1
> kind: BuildConfig
> metadata:
> name: sample-pipeline
> namespace: gulu
> selfLink: /oapi/v1/namespaces/gulu/buildconfigs/sample-pipeline
> uid: 12dec3c8-1948-11e7-a217-0251082287a6
> resourceVersion: '3757'
> creationTimestamp: '2017-04-04T15:05:00Z'
> labels:
> app: jenkins-pipeline-example
> name: sample-pipeline
> template: application-template-sample-pipeline
> annotations:
> pipeline.alpha.openshift.io/uses: >-
> [{"name": "nodejs-mongodb-example", "namespace": "", "kind":
> "DeploymentConfig"}]
> spec:
> triggers:
> - type: GitHub
> github:
> secret: secret101
> - type: Generic
> generic:
> secret: secret101
> runPolicy: Serial
> source:
> type: None
> strategy:
> type: JenkinsPipeline
> jenkinsPipelineStrategy:
> jenkinsfile: >-
> node('nodejs') {
> stage 'build'
> openshiftBuild(buildConfig: 'nodejs-mongodb-example', showBuildLogs:
> 'true')
> stage 'deploy'
> openshiftDeploy(deploymentConfig: 'nodejs-mongodb-example')
> }
> output: {}
> resources: {}
> postCommit: {}
> nodeSelector: null
> status:
> lastVersion: 1
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBTIS-1072) Update version in the standalone installer for 10.3.0.CR1-SNAPSHOT
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1072?page=com.atlassian.jira.plugin... ]
Andrej Podhradsky closed JBTIS-1072.
------------------------------------
Fix Version/s: 10.3.0.CR1
Resolution: Done
Verified. Now it contains
{code}
Installing com.jboss.devstudio.integration-stack.fuse.feature.feature.group 10.3.0.CR1-SNAPSHOT-v20170405-1507-B6.
Installing com.jboss.devstudio.integration-stack.soa.feature.feature.group 10.3.0.CR1-SNAPSHOT-v20170405-1507-B6.
Installing com.jboss.devstudio.integration-stack.bpr.feature.feature.group 10.3.0.CR1-SNAPSHOT-v20170405-1507-B6.
Installing com.jboss.devstudio.integration-stack.ds.feature.feature.group 10.3.0.CR1-SNAPSHOT-v20170405-1507-B6
{code}
> Update version in the standalone installer for 10.3.0.CR1-SNAPSHOT
> ------------------------------------------------------------------
>
> Key: JBTIS-1072
> URL: https://issues.jboss.org/browse/JBTIS-1072
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: build
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Fix For: 10.3.0.CR1
>
>
> The following installer
> {code}
> devstudio-integration-stack-10.3.0.CR1-SNAPSHOT-standalone-installer.jar
> {code}
> doesn't contain the appropriate version for devstudio-is features but the versions as follows
> {code}
> 10.2.0.CR1-SNAPSHOT-v20170320-1826-B2
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBTIS-985) Fuse: Fix smoke tests
by Tomáš Sedmík (JIRA)
[ https://issues.jboss.org/browse/JBTIS-985?page=com.atlassian.jira.plugin.... ]
Tomáš Sedmík edited comment on JBTIS-985 at 4/6/17 4:23 AM:
------------------------------------------------------------
Another issue on Windows
{code}
org.jboss.reddeer.common.exception.WaitTimeoutExpiredException: Timeout after: 10 s.: ContentAssistant shell is opened
at org.jboss.reddeer.common.wait.AbstractWait.timeoutExceeded(AbstractWait.java:183)
at org.jboss.reddeer.common.wait.AbstractWait.wait(AbstractWait.java:136)
at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:101)
at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:71)
at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:56)
at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:44)
at org.jboss.reddeer.common.wait.WaitUntil.<init>(WaitUntil.java:35)
at org.jboss.reddeer.workbench.impl.editor.AbstractEditor.openContentAssistant(AbstractEditor.java:179)
at org.jboss.tools.fuse.ui.bot.test.CamelEditorTest.testCodeCompletion(CamelEditorTest.java:193)
{code}
*NOTE*
I suspect that this issue is caused by slave settings (on my virtual machine with Windows it works). Try to adapt Windows settings - different way how to connect to Jenkins (JNLP) to ensure that test run is visible.
was (Author: tsedmik):
Another issue on Windows
{code}
org.jboss.reddeer.common.exception.WaitTimeoutExpiredException: Timeout after: 10 s.: ContentAssistant shell is opened
at org.jboss.reddeer.common.wait.AbstractWait.timeoutExceeded(AbstractWait.java:183)
at org.jboss.reddeer.common.wait.AbstractWait.wait(AbstractWait.java:136)
at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:101)
at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:71)
at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:56)
at org.jboss.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:44)
at org.jboss.reddeer.common.wait.WaitUntil.<init>(WaitUntil.java:35)
at org.jboss.reddeer.workbench.impl.editor.AbstractEditor.openContentAssistant(AbstractEditor.java:179)
at org.jboss.tools.fuse.ui.bot.test.CamelEditorTest.testCodeCompletion(CamelEditorTest.java:193)
{code}
> Fuse: Fix smoke tests
> ---------------------
>
> Key: JBTIS-985
> URL: https://issues.jboss.org/browse/JBTIS-985
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: Fuse IDE, QE
> Affects Versions: 4.4.0.Final
> Reporter: Tomáš Sedmík
> Assignee: Tomáš Sedmík
> Priority: Critical
> Fix For: 4.4.3.CR1
>
>
> Smoke tests are not stable ... fix them! :-)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBTIS-985) Fuse: Fix smoke tests
by Tomáš Sedmík (JIRA)
[ https://issues.jboss.org/browse/JBTIS-985?page=com.atlassian.jira.plugin.... ]
Tomáš Sedmík commented on JBTIS-985:
------------------------------------
Another issue on various operating systems
{code}
java.lang.AssertionError: Suspension was not performed
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.jboss.tools.fuse.ui.bot.test.JMXNavigatorTest.testContextOperations(JMXNavigatorTest.java:121)
{code}
*I skipped execution of this test temporary*
> Fuse: Fix smoke tests
> ---------------------
>
> Key: JBTIS-985
> URL: https://issues.jboss.org/browse/JBTIS-985
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: Fuse IDE, QE
> Affects Versions: 4.4.0.Final
> Reporter: Tomáš Sedmík
> Assignee: Tomáš Sedmík
> Priority: Critical
> Fix For: 4.4.3.CR1
>
>
> Smoke tests are not stable ... fix them! :-)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-23997) JBoss data source file schema error
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23997?page=com.atlassian.jira.plugi... ]
Josef Kopriva reassigned JBIDE-23997:
-------------------------------------
Assignee: Josef Kopriva
> JBoss data source file schema error
> -----------------------------------
>
> Key: JBIDE-23997
> URL: https://issues.jboss.org/browse/JBIDE-23997
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jst
> Affects Versions: 4.4.3.Final
> Reporter: Josef Kopriva
> Assignee: Josef Kopriva
> Fix For: LATER
>
>
> An error message is shown, when new datasource file is added to a project:
> {code:java}
> Description Resource Path Location Type
> cvc-elt.1: Cannot find the declaration of element 'datasources'. sa-ds.xml /testteast line 2 XML Problem
> {code}
> Datasource file:
> {code:java}
> <?xml version="1.0" encoding="UTF-8"?>
> <datasources xmlns="http://www.jboss.org/ironjacamar/schema">
> <datasource jndi-name="java:jboss/datasources/sa" enabled="true"
> use-java-context="true" pool-name="sa">
> <connection-url>jdbc:h2:tcp://localhost/sakila</connection-url>
> <driver>h2-1.3.161.jar</driver>
> <pool></pool>
> <security>
> <user-name>sa</user-name>
> <password></password>
> </security>
> </datasource>
> </datasources>
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBTIS-1072) Update version in the standalone installer for 10.3.0.CR1-SNAPSHOT
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1072?page=com.atlassian.jira.plugin... ]
Andrej Podhradsky updated JBTIS-1072:
-------------------------------------
Description:
The following installer
{code}
devstudio-integration-stack-10.3.0.CR1-SNAPSHOT-standalone-installer.jar
{code}
doesn't contain the appropriate version for devstudio-is features but the versions as follows
{code}
10.2.0.CR1-SNAPSHOT-v20170320-1826-B2
{code}
was:
The following installer
{code}
devstudio-integration-stack-10.3.0.CR1-SNAPSHOT-standalone-installer.jar
{code}
doesn't contain the appropriate version if devstudio-is features but the versions as follwos
{code}
10.2.0.CR1-SNAPSHOT-v20170320-1826-B2
{code}
> Update version in the standalone installer for 10.3.0.CR1-SNAPSHOT
> ------------------------------------------------------------------
>
> Key: JBTIS-1072
> URL: https://issues.jboss.org/browse/JBTIS-1072
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: build
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
>
> The following installer
> {code}
> devstudio-integration-stack-10.3.0.CR1-SNAPSHOT-standalone-installer.jar
> {code}
> doesn't contain the appropriate version for devstudio-is features but the versions as follows
> {code}
> 10.2.0.CR1-SNAPSHOT-v20170320-1826-B2
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24231) Unable to accept T&C when downloading EAP 7 in Eclipse
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24231?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-24231:
---------------------------------------
Linking JBIDE-21745 - a similar issue in the past. In that case, this happened when you used your @redhat.com account, but without the @redhat.com suffix. If you used the full name, it would work.
> Unable to accept T&C when downloading EAP 7 in Eclipse
> ------------------------------------------------------
>
> Key: JBIDE-24231
> URL: https://issues.jboss.org/browse/JBIDE-24231
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.4.4.AM2
> Reporter: Martin Malina
> Assignee: Rob Stryker
>
> I few days ago when I tried to download EAP 7 in JBoss Tools 4.4.0.AM2 while testing it, I was faced with this message instead of the T&C in the wizard:
> It is no longer possible to accept terms and conditions in the wizard. Please, use following link instead!
> I used my redhat.com account (mmalina1 at redhat.com). What's also curious is that I used this account many times in the past, so it's strange that I was required to accept the T&C in the first place.
> I was able to log in inside that window (where normally just the text would be displayed) and then got this message:
> {code}
> You Entered All Necessary Information
> Thank you for filling all necessary information. Now you can go back to Eclipse and retry your download of /jboss-eap-7.0.0.Beta.zip.
> {code}
> When I went back and forth, I was then able to download the runtime successfully. So I'm afraid I won't be able to reproduce this unless somebody resets my account.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24231) Unable to accept T&C when downloading EAP 7 in Eclipse
by Martin Malina (JIRA)
Martin Malina created JBIDE-24231:
-------------------------------------
Summary: Unable to accept T&C when downloading EAP 7 in Eclipse
Key: JBIDE-24231
URL: https://issues.jboss.org/browse/JBIDE-24231
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: runtime-detection
Affects Versions: 4.4.4.AM2
Reporter: Martin Malina
Assignee: Rob Stryker
I few days ago when I tried to download EAP 7 in JBoss Tools 4.4.0.AM2 while testing it, I was faced with this message instead of the T&C in the wizard:
It is no longer possible to accept terms and conditions in the wizard. Please, use following link instead!
I used my redhat.com account (mmalina1 at redhat.com). What's also curious is that I used this account many times in the past, so it's strange that I was required to accept the T&C in the first place.
I was able to log in inside that window (where normally just the text would be displayed) and then got this message:
{code}
You Entered All Necessary Information
Thank you for filling all necessary information. Now you can go back to Eclipse and retry your download of /jboss-eap-7.0.0.Beta.zip.
{code}
When I went back and forth, I was then able to download the runtime successfully. So I'm afraid I won't be able to reproduce this unless somebody resets my account.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years