[JBoss JIRA] (SWSQE-93) Create internal git repository
by Filip Brychta (JIRA)
Filip Brychta created SWSQE-93:
----------------------------------
Summary: Create internal git repository
Key: SWSQE-93
URL: https://issues.jboss.org/browse/SWSQE-93
Project: Swift Sunshine QE
Issue Type: Sub-task
Reporter: Filip Brychta
Assignee: Michael Foley
We need internal git repository for things like:
* dockerfiles for jenkins docker slaves
* openshift templates
* installation scripts
Part of this task is to investigate options we have for internal git repositories (there is not just one)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (SWSQE-92) Set up jenknins master
by Filip Brychta (JIRA)
Filip Brychta created SWSQE-92:
----------------------------------
Summary: Set up jenknins master
Key: SWSQE-92
URL: https://issues.jboss.org/browse/SWSQE-92
Project: Swift Sunshine QE
Issue Type: Sub-task
Reporter: Filip Brychta
Assignee: Michael Foley
Currently we have http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/
It's a VM running in rhev. We need to:
* set up HA in rhev
* check storage config to use RAID5 storage
* check installed plugins and remove unused
* check security configuration
* set up backup of master using thin backup
* document best practices
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (SWSQE-91) Create "production" setup for CI
by Filip Brychta (JIRA)
[ https://issues.jboss.org/browse/SWSQE-91?page=com.atlassian.jira.plugin.s... ]
Filip Brychta updated SWSQE-91:
-------------------------------
Description:
Currently we have PoCs located in different personal repos, jenkins2 is not properly backuped and so on.
Will add sub-tasks for jenkins2 master, jenkins docker slaves, create git repo for that....
was:Will add sub-tasks for jenkins2 master, jenkins docker slaves, create git repo for that....
> Create "production" setup for CI
> --------------------------------
>
> Key: SWSQE-91
> URL: https://issues.jboss.org/browse/SWSQE-91
> Project: Swift Sunshine QE
> Issue Type: Task
> Reporter: Filip Brychta
> Assignee: Filip Brychta
>
> Currently we have PoCs located in different personal repos, jenkins2 is not properly backuped and so on.
> Will add sub-tasks for jenkins2 master, jenkins docker slaves, create git repo for that....
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (DROOLS-2420) [DMN Designer] Hit Policy Collect does not need an Aggregation function
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2420?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2420:
--------------------------------
Description:
Page 86 of the OMG DMN1.1 Specification states "...if the aggregation attribute is not specified, the value of the decision table is the unordered set itself;"
h2. Acceptance test
# After saving and reopening is user able to achieve Collect hit policy (/)
## with aggregating function
## without aggregating function
# After saving and reopening is user able to change (/)
## From any collect hit policy to non collect hit policy
## From non collect hit policy to collect hit policy
# Change of hit policy is reflected in dmn file (/)
# Change of hit policy will show aggregation function just if Collect hit policy, otherwise None
was:
Page 86 of the OMG DMN1.1 Specification states "...if the aggregation attribute is not specified, the value of the decision table is the unordered set itself;"
h2. Acceptance test
# After saving and reopening is user able to achieve Collect hit policy (/)
## with aggregating function
## without aggregating function
# After saving and reopening is user able to change (/)
## From any collect hit policy to non collect hit policy
## From non collect hit policy to collect hit policy
# Change of hit policy is reflected in dmn file (/)
> [DMN Designer] Hit Policy Collect does not need an Aggregation function
> -----------------------------------------------------------------------
>
> Key: DROOLS-2420
> URL: https://issues.jboss.org/browse/DROOLS-2420
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
>
> Page 86 of the OMG DMN1.1 Specification states "...if the aggregation attribute is not specified, the value of the decision table is the unordered set itself;"
> h2. Acceptance test
> # After saving and reopening is user able to achieve Collect hit policy (/)
> ## with aggregating function
> ## without aggregating function
> # After saving and reopening is user able to change (/)
> ## From any collect hit policy to non collect hit policy
> ## From non collect hit policy to collect hit policy
> # Change of hit policy is reflected in dmn file (/)
> # Change of hit policy will show aggregation function just if Collect hit policy, otherwise None
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (ELY-1035) CS tool, Error msg with mutually exclusive parameters must contain "really" used option names.
by Ilia Vassilev (JIRA)
[ https://issues.jboss.org/browse/ELY-1035?page=com.atlassian.jira.plugin.s... ]
Ilia Vassilev commented on ELY-1035:
------------------------------------
[~hsvabek] Are you ok with closing this issue since this functionality depend on apache commons-cli implementation and the way it handles exclusive options error. Thanks!
> CS tool, Error msg with mutually exclusive parameters must contain "really" used option names.
> ----------------------------------------------------------------------------------------------
>
> Key: ELY-1035
> URL: https://issues.jboss.org/browse/ELY-1035
> Project: WildFly Elytron
> Issue Type: Bug
> Reporter: Hynek Švábek
> Assignee: Ilia Vassilev
>
> When we use more mutually exclusive parameters (add, remove) then we get error message. But this message contains only short version of option names.
> "r" instead of "remove"
> "a" instead of "add"
> {code}
> [hsvabek@localhost bin]$ java -jar wildfly-elytron-tool.jar credential-store --add myalias --secret supersecretpassword --location="test.store" --uri "cr-store://test.store?modifiable=true;create=true;keyStoreType=JCEKS" --password mycspassword --summary --salt 12345678 --iteration 230 --remove
> The option 'r' was specified but an option from this group has already been selected: 'a'
> {code}
> *Same for "credential-store" command.*
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (SWSQE-91) Create "production" setup for CI
by Filip Brychta (JIRA)
Filip Brychta created SWSQE-91:
----------------------------------
Summary: Create "production" setup for CI
Key: SWSQE-91
URL: https://issues.jboss.org/browse/SWSQE-91
Project: Swift Sunshine QE
Issue Type: Task
Reporter: Filip Brychta
Assignee: Filip Brychta
Will add sub-tasks for jenkins2 master, jenkins docker slaves, create git repo for that....
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month