alm Questions

Tools like JIRA, Service Now for Incident management, I'm looking for a software platform that will keep track of all related documentation, test plans, user sign offs etc... But what I have not been able to find and is critical for me is a Parent - Child, Child - Child relationship of all changes.

Such as:

CR12345 - is the parent record

  CR12345A - is a child record to CR12345

     CR12345A1 - is a child record of CR12345A

CR12345B is a child record to CR12345

Has anyone seen software that can support this? 

Hello,

I have a number of Linux shell scripts for automation of particular operations. For example: merging SVN revisions from one branch to other, update statuses of JIRA tickets, make an Oracle eBS build from sources stored in SVN or git etc. 

I'm trying to use these automation scripts for different infrastuctures and customers. But I cannot share the script code for mentioned customers. Is it possible to put automation shell scripts in cloud and call these scripts from different infrastuctures? Are some available technical solutions how to call Linux shell scripts from cloud?

For example in cloud I could have shell function svn_merge() with parameters. But this script could be called from different infras with different parameters like "svn_merge <parameters>".

I will be happy to see any suggestions, any links to any free or commercial solutions.

 

Thanks in advance!

Arturs

 

In practice I have two new features that are under change control and that I want to be able to track them as separate changes from the first change and until the features are deployed to production.
 
How do I handle the fact that they both need to make the same changes to one part of the code? If I let one of them carry the change but then decides later on to back out of that “Feature” then I  will break the other feature that where depending on the same change. 
 
I am curious to know of any good advice or best practices to use i CM when dealing with those type of scenarios. 
 
We use MS TFS as version control and status accounting tool, but I am really interested in learning about best practice in general.
 
Thanks Johan.

By Paul Perry - December 18, 20151 Answer

Hello Everyone,

I'd like to understand how companies using SVN, TFS, Git, GitHub perform backing out production deployments from two perspectives, your re-deployment method but more importantly, how are you indicating in your respective repo that if code was rolled back, what are you doing internally with your SCM tool to force a message to developers that code was backed out.

Thanks

Paul Perry

I'm looking for any suggestions anybody might have of real parameters that are mesurable and could be used to improve the quality and robustness of Configuration Management Business Cases to encourage the adoption of CM as early as possible in new programmes and projects

Hi. I have been looking around for new references to the software CA Harvest SCM and until now have not been able to identify this solution in recent independant studies (for example, Gartner Magic Quadrant, Forrester Wave, or others).  Does anyone know why  Harvest is not included in the recent versions of these reports?

 

 

Regards,

A new project we got will force us to add a few more testers for the duration of the project (estimated around 8 months). We will probably outsource this extra testing alongside us. My question really has to do with any advice or tool anyone of you uses or knows of that will be a smart way to manage this effort?

Question title may not be specific enough and I feel like I could right a book but I'll try to keep it concise.

 

Configuration example Freight configurations (3 tables)

 

First process attempt:

 

Resource took BA configuration Word document that came out of system study

 

Resource wrote SQL and XML patches and checked them into source control

 

Above step was initial configuration of the customer's application data

 

Patches were packaged up into Release Package with source and schema changes and were installed by install utility

 

Over time developer adds configurations as features were implemented.  These were also SQL and XML patches checked into source control

 

Over time QA adds configurations as features were implemented or new application configurations were discovered

 

Problem is what happens when the application is installed in UAT and the client uses the UI to make application configurations (Note: client cannot be expected to track their own changes and

sometimes they are comprehensive enough such as menu reconfigurations they don't want to do by hand to promote to PRD)

 

Second process attempt:

 

Instead of creating SQL and XML patches a Config tool was established.  Required application to be installed and running.

 

Resource took BA configuration Word document that came out of system study

 

Resource installed the app and manually made configurations through application UI (some configs don't have UI interface and those were done manually in the DB)

 

Developer uses the configuration file resource put together to get his development going

 

Over time developer documents configurations and doesn't patch them.  Developer and QA manually applies configurations with feature changes.

 

Over time QA adds configurations as features were implemented or new application configurations were discovered.  This configuration file was used to promote.

 

Client gets in UAT environment and makes configuration changes via the UI.  Just need to recreate the configuration file

 

Problem is the configuration xml file (just more than freight, it was just an example) is hard to compare between environments to figure out the differences.  Not sorted and displayed well 

for text XML comparison tools.  Configuration handles adding but no deleting.  Configuration tool requires app to be up and running.  Configuration doesn't account for configurations that

were in place for only testing and don't want those to be promoted to PRD.

 

Third process attempt:

 

Sort of did second process but then went to just completely manually updating and tracking changes via UI, saving off Configuration as a backup.  Problem is very manual and error

proned missed settings

 

 

Conclustion:

 

Looking for process of how to handle this sort of thing through ALM and CM, considering the challenges mentioned above.  Can fix the configuraiton tool to present data for better XML

comparision tool.  Can make configuration tool run as a utility outside of the app running.  can use something like Redgate SQL Data Compare (but must setup views, note keys can be different

between promotion environments).  What should be done process-wise to manage and track "real/wanted" configuration changes.

 

Hope this is making sense.

CM, ALM Engineer in Toronto, ON - web, tfs, sql - [email protected]

By BenN - April 19, 20131 Answer

Hi all,

We are currently implementing agile, and have a fully realised development cycle in place.  I have now been tasked with implementing a deployment tech stack.  We are currently running a Subversion repository, feeding in to a Jenkins / Maven continuous integration platform, and an Artefactory Repository for compiled code.  We then have no path out of Artefactory (at the moment, the devs are packaging up complete WARs of the environment and copying manually to the target area).  I want to implement a continuous deployment solution, that can be used by developers for small fixes and by tech leads for large releases.

I have looked around but am struggling to find a tool to realise this that will integrate with our current tech (everything seems to want to replace Jenkins etc with their own agent based build / test / artifact solution).  Does anyone know of software that will allow me to automate the movement of compiled code from our dev platform to  our test environment, then on to prod, setting rules and checks along the way? 

Many thanks in advance,

Ben

Pages

CMCrossroads is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.