ATC checks with behaviour 'block'

[christianpunz]

hi!

we discussed how we can maintain (and enforce) code quality with NEW code. We have seen the drop-down-field 'Behavior on Release' in TCODE ATC. At the moment it is 'X=inform'. We would like to have an 'E=block', BUT ONLY FOR NEWLY BORN CODE starting with a defined calendar day.

Due to the vast amount of legacy code which will not comply with the tailor made check variant (DEFAULT+PERFORMANCE_DB+FUNCTIONAL_DB) we would not be able to maintain legacy code with setting 'E=block'.

I debugged the whole transport order release (CL_SATC_AC_TRANSPORT_CHECK) but did not see a chance to make an easy enhancement there.

Any feedback appreciated!

br

chris

olga.dolinskaja, are you able to help here?

[ceedee666]

Hi Christian,

In the latest version of the ATC there is the baseline feature: https://blogs.sap.com/2016/12/13/remote-code-analysis-in-atc-working-with-baseline-to-suppress-findi...

The feature basically accepts the current state of the code base and only enforces the ATC rules for new or changed code. Isn’t this exactly what you need? Basically all new code and all changed legacy code needs to conform to the code quality requirements. And if you change legacy code that you relay can’t fix for whatever reason you can allways add another exception.

Christian

[christianpunz]

hi Christian,

thx for your contribution!

Unfortunately very few of my customers have a remote ATC in use. I hoped to find a secret switch in a 'normal' dev-system (let's say 7.50) of a common 3-tier-landscape - w/o the need of a further system for remote ATC.

br

chris

[BaerbelWinkler]

christian.punz

Hi Christian,

I don't think that there is a means to use something like the baseline concept without a (central) NW 752 System for ATC-checks. As explained in my blog series about setting up our central ATC-system we couldn't switch on blocking on transport release immediately after updating our system to HANA DB for exactly the issues you mention.

Cheers

Bärbel

[thomas_schulzezurwiesch]

Hi Christian,

if you are not yet on the minimum release for the baseline feature (7.51), you might want to check the ATC remote scenario, which allows you to scan systems on older releases from a so called central check system on a higher release: https://blogs.sap.com/2016/12/12/remote-code-analysis-in-atc-one-central-check-system-for-multiple-s...

There is also a way to run the checks then in the development tools and on transport release (certain minimum SPs required). More information can be found in this blog: https://blogs.sap.com/2017/02/27/remote-code-analysis-in-atc-for-developers/

Best regards,

Thomas