Scoping a flow target of repository workspace in RTC Command line Interface - rtc

I have a repository workspace which has a default flow target. I want to edit the flow target and make it scoped only for few components. This is possible from RTC Eclipse Client. How can I achieve the same from RTC command line Interface. Please tell with reference to RTC 3.0.1.3.

I am not sure if that API works for 3.x, or only for 4.x, but this sequence of lscm commands seems to produced a scoped flow target:
# Set a component as the flow target
$ lscm workspace flowtarget TestWorkspace1 TestStream1 -C TestComp2 -r lo
Successfully updated the flow target.
# View workspace flow target that was scoped to specific components
$ lscm workspace flowtarget TestWorkspace1 TestStream1 -r <repo>
(1352) "TestStream1" (scoped) (current)
The following components flow from/to this flow target:
(1351) "TestComp2"
You can see that command introduced in the Rational Team Concert 4.0.1 M4 Milestone, so it is possible isn't available in RTC3.x.

Related

How do i create an RTC Baseline on a component in a stream using scm.exe?

After building software from files from an RTC stream, I want to create a baseline of the component as a record of the state of the files.
It needs to be automated, hence the use of SCM.
I want to create it in a single step if I can, i.e, not create baseline on the component in a workspace, then deliver it.
I can create a baseline on a component in a workspace using:
scm.exe create baseline -r Repository -u username -P password "workspace" "Baseline name" "Component name"
Alternatively, how can I automatically deliver the baseline in the workspace above, or should I be using snapshots?
I am not aware of creating a baseline in a single step.
If you can create it in a dedicate workspace with, as a default flow target, the right stream, you should be able to call scm deliver (examples), as mentioned here:
scm deliver: scm deliver -r <repo> -s <source_stream> -t <target_stream> -b <baseline_uuid_or_name>
Or simply:
scm deliver -C <component>
Since it would deliver all changesets and baselines for that component.

Spring Profiles in combination with ConfigServer

I have a very basic Spring Boot Config Server (just added the dependency and annotated mainclass with #EnableConfigServer).
In general I would like to support multiple environments with different propertysources for each of my applications, here is the example of the ConfigServer itself:
Profile: default (application.yml on classpath):
Profile: docker (application-docker.yml on classpath):
Profile: default (application.yml in repository of ConfigServer):
So in my case all of the properties from all of the three screenshots should be active, I'd expect the order/priority as follows:
application.yml from classpath
application-ANY_PROFILE.yml from classpath
application.yml from config repo
APP-NAME.yml from config repo (does not exists in this case)
So far this works flawlessly, except the issue that I'm having is that my application-docker.yml on classpath is beeing ignored when I start the application with the command (of course inside the container):
java -jar -Dspring-boot.run.profiles=docker *.jar
as you can see here:
My question is, even when I provide the profile as command line argument its not beeing picked up.
Why is that?
UPDATE, here is the Dockerfile and entrpoint.sh:
To activate one or more profiles do one of the following:
Activate using the VM parameters -Dspring.profiles.active=<profiles>
Activate using program arguments --spring.profiles.active=<profiles>
Following your example, the following should work:
java -jar -Dspring.profiles.active=docker *.jar

How to disable simultaneous build on drone io?

I use drone as CI and want to know how I can disable simultaneous build. What's happening is that when I submit two commits to git repo, drone will trigger two build on each of the submit. How can I let the second build wait until the first one finish?
Regarding the open source version of Drone: set the DOCKER_MAX_PROCS environment variable of your drone agent to 1, i.e. docker run -e DOCKER_MAX_PROCS=1 [...] drone/drone:0.5 agent. The agent will run one build concurrently, other builds will queue up.
See the Installation Reference section in the readme for more info.

Build information in server group

The Clusters-tab in the Spinnaker web UI shows my Server Groups and their deployment version (V000 ... Vn). Next to the deployment version, some build information is displayed, which in my Spinnaker instance is always (No build info).
Is there a way to add some build info, for example a Git commit/tag or Docker tag?
Right now the build info is based on the jenkins build information. It derives this information from the ami tags appversion and build_host to link back to jenkins. appversion has to follow a defined schema, see this comment in the Rosco source code for example.
You cannot customize these values at this point, but a pull request is welcome

Flow in JetBrains/IntelliJ IDEA

It seems like JetBrains supports Flow type checker but I'm not seeing the flow error in the IDE.
Is there a way to enable it?
Flow Type Checker is not yet supported, please follow WEB-14254 for updates.
Idea just supports Flow syntax (static typing). See http://blog.jetbrains.com/webstorm/2015/09/webstorm-11-eap-142-5255/
I've put together an experimental plugin integrating Flow error reports into IDEA/WebStorm as error annotations:
https://github.com/dsilva/webstorm-plugin-flow-typecheck/releases
#lena is correct.
As an aside, I run flow through the npm panel. As long as flow is a script in your package.json, I run in by right-clicking on package.json and Show npm scripts. Then just double click on flow or re-run it as needed in the Run panel.
As of Nov 2016 Jetbrains Webstorm / IntelliJ IDEA now supports Flow:
https://blog.jetbrains.com/webstorm/2016/11/using-flow-in-webstorm/
In Settings -> Languages & Frameworks -> Javascript select Flow
Running Flow Server in WebStorm
check the version of your flow-bin, only 0.59.0 works with WebStorm.
run this command to install flow-bin globally:
npm i -g flow-bin#0.59.0
Adding flow config file to your project
npm flow init
finding node-modules global path : copy this path , We will use it in WebStorm settings.
npm list -g
WebStorm Setting :
Go to here :
File > Settings > languages and Frameworks > Javascript
Select flow in drop-down menu.
In Flow executable paste global path of flow-bin (local path doesn't work). and with three dots button select the proper folder for your operating system.
In Use-Flow-server-for section tick Type checking box and then hit Apply button.
Find this section in settings :
Editor > Inspections > Javascript > Flow Type Checker
ensure Flow errors check box is active
Hit Apply and Ok
After that flow server should be started when you open project in Webstorm.
Don't forget to put
// #flow
at top of your files.