I have test cases setup for my project; the builds go through however test cases are not being executed. ATF is enabled on the instance and the ATF user is created with the correct roles; also ATF is launching as part of the build but not the test cases; I am getting the below:

Execute ATF: Wrapper
execute Mocha Tests...

Execute ATF: Execution Issue
√ >>>>> Passing for now, but no test cases specified!

1 passing (8ms)
[17:29:28] Finished 'test' after 8.23 s

Task Ended 'test'

ZIP: test adding folder C:\Users\user1\AppData\Local\Temp\2\ac6be813-8f0a-4faf-b6b5-a556f205f1f3\test
[17:29:28] Starting 'build'...

Starting Task 'build'

Build Done: Thanks for submitting
[17:29:28] Finished 'build' after 230 ms

Task Ended 'build'

No config found for task 'build'
ZIP: test 359935 total bytes
ZIP: test archiver has been finalized and the output file descriptor has closed.
Upload Results test Upload successful! Server responded with: File uploaded!

What am I missing?

hi,
getting the below error in node when i click on build this application ui action in servicenow. can you help?

[01:48:35.102] [LOG] [19196] [/worker#lwLR4eV-RSALbmdVAAAA] Starting module: projectSetup
[01:48:35.105] [LOG] [19196] [/worker#lwLR4eV-RSALbmdVAAAA] STARTING PROMISE JOB 'projectSetup'
[01:48:35.112] [ERROR] [19196] [/worker#lwLR4eV-RSALbmdVAAAA] PROMISE JOB ERROR: Job 'projectSetup' { type: 'exe',
name: 'projectSetup',
options:
{ updateSet: '261c169d1b9c48106933fc88cc4bcb2b',
application:
{ id: '268e9d5fdbb32300fcf417803996195e',
name: 'CICD Test Application' },
requestor:
{ userName: 'admin',
fullName: 'System Administrator',
email: '[email protected]' },
atf: { updateSetOnly: false },
git: { repository: 'x_11413_cicd_test' },
source: { name: 'https://dev1234.service-now.com/' },
master: { name: null },
target: { name: null } },
host: 'LAPTOP-JS3P7BMM',
id: '4ef3da58-0405-4c17-8d50-87f0474dac90',
emitter: { _events: {}, _eventsCount: 2 },
created: 1570168115100,
completed: null,
workerId: '/worker#lwLR4eV-RSALbmdVAAAA',
result: undefined,
error: undefined } Error: Configuration Error: source server host name not defined in config.host.name
at Promise.try (C:\Users\ganes\Desktop\sn-cicd-master\sn-cicd-master\lib\modules\project-setup.js:198:23)
at tryCatcher (C:\Users\ganes\Desktop\sn-cicd-master\sn-cicd-master\node_modules\bluebird\js\release\util.js:16:23)
at Function.Promise.attempt.Promise.try (C:\Users\ganes\Desktop\sn-cicd-master\sn-cicd-master\node_modules\bluebird\js\release\method.js:39:29)
at CICD.configure (C:\Users\ganes\Desktop\sn-cicd-master\sn-cicd-master\lib\modules\project-setup.js:191:27)
at CICD.module.exports (C:\Users\ganes\Desktop\sn-cicd-master\sn-cicd-master\lib\modules\project-setup.js:497:22)
at Promise.try.then (C:\Users\ganes\Desktop\sn-cicd-master\sn-cicd-master\lib\eb\run-module.js:75:34)
at tryCatcher (C:\Users\ganes\Desktop\sn-cicd-master\sn-cicd-master\node_modules\bluebird\js\release\util.js:16:23)
at Promise._settlePromiseFromHandler (C:\Users\ganes\Desktop\sn-cicd-master\sn-cicd-master\node_modules\bluebird\js\release\promise.js:517:31)
at Promise._settlePromise (C:\Users\ganes\Desktop\sn-cicd-master\sn-cicd-master\node_modules\bluebird\js\release\promise.js:574:18)
at Promise._settlePromiseCtx (C:\Users\ganes\Desktop\sn-cicd-master\sn-cicd-master\node_modules\bluebird\js\release\promise.js:611:10)
at _drainQueueStep (C:\Users\ganes\Desktop\sn-cicd-master\sn-cicd-master\node_modules\bluebird\js\release\async.js:142:12)
at _drainQueue (C:\Users\ganes\Desktop\sn-cicd-master\sn-cicd-master\node_modules\bluebird\js\release\async.js:131:9)
at Async._drainQueues (C:\Users\ganes\Desktop\sn-cicd-master\sn-cicd-master\node_modules\bluebird\js\release\async.js:147:5)
at Immediate.Async.drainQueues [as _onImmediate] (C:\Users\ganes\Desktop\sn-cicd-master\sn-cicd-master\node_modules\bluebird\js\release\async.js:17:14)
at runCallback (timers.js:705:18)
at tryOnImmediate (timers.js:676:5)
at processImmediate (timers.js:658:5)

if an app contains multi scope, the deployment is triggered for each scope (correct) but the content of the us is wrong and always the same

Running into a deployment issue with 2 Orlando instances. The pipeline breaks at update set preview step on the instance. The error logged is as follow:
'Could not find a record in sys_app_category for column category referenced in this update'

Looked it up in the sys_app_category table and did not find a "category" column there on either sides (source or target); also checked the same tables on 2 previews versions (New York & Madrid) and tables are similar like the Orlando one.

I looked up the pull request in Git for the scoped app and looked at the exported XML and noticed the tag with a default value "customer" in there in many places; I was wondering if the process was complaining about it; even though the same process runs fine in New York & Madrid. Wondering what's breaking the process in Orlando.

Logs below:

[22:38:54.978] [LOG] [30032] Request: https://dev88759.service-now.com/api/devops/cicd/deploy_step?__step=previewUpdateSet&__status=304
[22:38:55.291] [LOG] [30032] Job in progress. Wait for 1000 ms ...
[22:38:56.294] [LOG] [30032] Request: https://dev88759.service-now.com/api/devops/cicd/deploy_step?__step=previewUpdateSet&__status=304
[22:38:56.651] [LOG] [30032] Request: https://dev88759.service-now.com/api/devops/cicd/deploy_step?__step=commitUpdateSet&__status=303
[22:38:56.990] [ERROR] [30032] [/worker#hOdmxdADXHiF0GxlAAAC] deploy-update-set.deployUpdateSet : Commit requires manual interaction! - Update conflicts must be resolved manually. { name: 'Preview Review Problem',
message: '- Update conflicts must be resolved manually. ',
updateSet:
'https://dev88759.service-now.com/sys_remote_update_set.do?sys_id=941a68681b8b5010271ced3abc4bcb89',
issues: true,
previewProblems:
[ { type: 'error',
name:
'Could not find a record in sys_app_category for column category referenced in this update',
link:
'https://dev88759.service-now.com/sys_update_preview_problem.do?sys_id=ba1aa8681b8b5010271ced3abc4bcb3e' } ],
dataLossWarnings: [],
payload:
{ version: null,
sourceSysId: 'd9f4edf71b321010271ced3abc4bcb72',
targetEnvironment: 'https://dev88759.service-now.com/',
updateSetSysId: '54dca2c77a76f3d36b4d6dde84a86503',
limitSet: [ '4VQVmZl3hVXr2A6B' ],
sourceEnvironment: 'https://dev91367.service-now.com',
deploy: true,
collisionDetect: false,
conflicts: { resolutions: {}, defaults: [Object] },
step: 'commitUpdateSet',
progressId: null,
state: 'previewed',
remoteUpdateSetSysId: '941a68681b8b5010271ced3abc4bcb89',
missingRecords: {} } }
[22:38:58.482] [WARN] [30032] Email notification is disabled. Following message was not sent: "DevOps Integration" <>, DEPLOYMENT CONFLICTS - Update Set is causing conflicts: Deployment of 'my_demo_app - 1.0.0 › #1' requires manual interaction

Deployment Conflicts in Update Set 'my_demo_app - 1.0.0 › #1'

The 'preview' step during the update set deployment on target https://dev88759.service-now.com detected conflicts and requires them to be resolved manually.

Please open the Target Update Set and resolve all conflicts to proceed with this deployment.

Update conflict:

user lookup fails for git delete commit as payload xml does has empty <sys_updated_by> and <sys_created_by> tags

During multi scope deployment the scope of the initiated US is taken during deployment instead of each individual one.

Issue:
config snippet from .env file :

# user to load update-set form 'source' and 'master'
CICD_CI_USER_NAME=svc_cicd
CICD_CI_USER_PASSWORD=*****

# user to deploy update-set to 'target'
CICD_CD_USER_NAME=admin
CICD_CD_USER_PASSWORD=****

while running deployment jobs, it always using 'admin' to connect to the source instance, it will cause authentication failure

{ error:
   { message: 'User Not Authenticated',
     detail: 'Required to provide Auth information' },
  status: 'failure' }

The pipeline was working fine between both my instances -now it is breaking with Remote update-set not found exception at the deployment stage; It's failing for existing applications and also for applications created from scratch,

What is the reason behind this exception? How can we fix it?

workerId: '/worker#zpr5LetrJJeqMv9yAAAB',
result: 'BACKGROUND-JOB-IN-PROGRESS',
error:
{ StatusCodeError: 400 - {"error":{"detail":"","message":"Remote update-set not found with "remote_sys_id" 3f2434266a5a6800d7ae05b98e08b293"},"status":"failure"}
at new StatusCodeError (C:\Users\user1\Documents\sncicd-server\node_modules\request-promise-core\lib\errors.js:32:15)
at Request.plumbing.callback (C:\Users\user1\Documents\sncicd-server\node_modules\request-promise-core\lib\plumbing.js:104:33)
at Request.RP$callback [as _callback] (C:\Users\user1\Documents\sncicd-server\node_modules\request-promise-core\lib\plumbing.js:46:31)
at Request.self.callback (C:\Users\user1\Documents\sncicd-server\node_modules\request\request.js:185:22)
at Request.emit (events.js:198:13)
at Request. (C:\Users\user1\Documents\sncicd-server\node_modules\request\request.js:1154:10)
at Request.emit (events.js:198:13)
at Gunzip. (C:\Users\user1\Documents\sncicd-server\node_modules\request\request.js:1076:12)
at Object.onceWrapper (events.js:286:20)
at Gunzip.emit (events.js:203:15)
at endReadableNT (_stream_readable.js:1145:12)
at process._tickCallback (internal/process/next_tick.js:63:19)
name: 'StatusCodeError',
statusCode: 400,
message:
'400 - {"error":{"detail":"","message":"Remote update-set not found with \"remote_sys_id\" 3f2434266a5a6800d7ae05b98e08b293"},"status":"failure"}',
error: { error: [Object], status: 'failure' },
options:
{ json: true,
baseUrl: null,
gzip: true,
encoding: 'utf8',
headers: [Object],
jar: false,
rawResponse: true,
autoPagination: true,
retry: 1,
delay: 100,
auth: [Object],
followRedirect: false,
method: 'POST',

The Slack PR message currently must come from the Git system, the CICD server is not capable to send that information directly (however it is exposing an API to the Git system to send slack messages)

Extend the CICD server to send PR Slack messages directly as discussed here
#30 (comment)

Install Node App steps fails as follow - Please advise.

[12:11:44.983] [LOG] [10336] Using SYS_* Field White-List 'sys_class_name, sys_created_by, sys_created_on, sys_id, sys_mod_count, sys_name, sys_package, sys_policy, sys_scope, sys_update_name, sys_updated_by, sys_updated_on'
[12:11:44.983] [LOG] [10336] Project Datastore: use remote
[12:11:44.985] [LOG] [10336] [/worker#ZbGaE-8YwQO-wT-JAAAA] build-project : install node application
[12:11:45.015] [LOG] [10336] install node app in C:\Users\user1\AppData\Local\Temp\3\git-root\459c6b10-47eb-4605-be75-f78bffe92478 [ 'ci', '--silent', '--no-audit', '--no-optional' ]
[12:11:55.729] [LOG] [10336] npm install process exited with code: 1
[12:11:55.730] [ERROR] [10336] [/worker#ZbGaE-8YwQO-wT-JAAAA] build-project : install node application failed:
Error
at C:\Users\user1\Documents\sncicd-server\node_modules\sn-cicd\lib\modules\build-project.js:41:76
at tryCatcher (C:\Users\user1\Documents\sncicd-server\node_modules\bluebird\js\release\util.js:16:23)
at Promise._settlePromiseFromHandler (C:\Users\user1\Documents\sncicd-server\node_modules\bluebird\js\release\promise.js:547:31)
at Promise._settlePromise (C:\Users\user1\Documents\sncicd-server\node_modules\bluebird\js\release\promise.js:604:18)
at Promise._settlePromise0 (C:\Users\user1\Documents\sncicd-server\node_modules\bluebird\js\release\promise.js:649:10)
at Promise._settlePromises (C:\Users\user1\Documents\sncicd-server\node_modules\bluebird\js\release\promise.js:725:18)
at _drainQueueStep (C:\Users\user1\Documents\sncicd-server\node_modules\bluebird\js\release\async.js:93:12)
at _drainQueue (C:\Users\user1\Documents\sncicd-server\node_modules\bluebird\js\release\async.js:86:9)
at Async._drainQueues (C:\Users\user1\Documents\sncicd-server\node_modules\bluebird\js\release\async.js:102:5)
at Immediate.Async.drainQueues [as _onImmediate] (C:\Users\user1\Documents\sncicd-server\node_modules\bluebird\js\release\async.js:15:14)
at processImmediate (internal/timers.js:456:21) Error
at C:\Users\user1\Documents\sncicd-server\node_modules\sn-cicd\lib\modules\build-project.js:41:76
at tryCatcher (C:\Users\user1\Documents\sncicd-server\node_modules\bluebird\js\release\util.js:16:23)
at Promise._settlePromiseFromHandler (C:\Users\user1\Documents\sncicd-server\node_modules\bluebird\js\release\promise.js:547:31)
at Promise._settlePromise (C:\Users\user1\Documents\sncicd-server\node_modules\bluebird\js\release\promise.js:604:18)
at Promise._settlePromise0 (C:\Users\user1\Documents\sncicd-server\node_modules\bluebird\js\release\promise.js:649:10)
at Promise._settlePromises (C:\Users\user1\Documents\sncicd-server\node_modules\bluebird\js\release\promise.js:725:18)
at _drainQueueStep (C:\Users\user1\Documents\sncicd-server\node_modules\bluebird\js\release\async.js:93:12)
at _drainQueue (C:\Users\user1\Documents\sncicd-server\node_modules\bluebird\js\release\async.js:86:9)
at Async._drainQueues (C:\Users\user1\Documents\sncicd-server\node_modules\bluebird\js\release\async.js:102:5)
at Immediate.Async.drainQueues [as _onImmediate] (C:\Users\user1\Documents\sncicd-server\node_modules\bluebird\js\release\async.js:15:14)
at processImmediate (internal/timers.js:456:21)
[12:11:55.737] [LOG] [10336] [/worker#ZbGaE-8YwQO-wT-JAAAA] build-project : cleaning up project
[12:11:55.740] [LOG] [10336] deleting C:\Users\user1\AppData\Local\Temp\3\git-root\459c6b10-47eb-4605-be75-f78bffe92478\node_modules
[12:11:57.512] [ERROR] [10336] [/worker#ZbGaE-8YwQO-wT-JAAAA] PROMISE JOB ERROR: Job 'buildProject' {
type: 'exe',
name: 'buildProject',
options: 'xUauor5G8AKEmCLY',
host: 'ncias-d2371-c',
id: '0895740f-60fe-41ee-990b-09621667cfb5',
emitter: { _events: {}, _eventsCount: 2 },
created: 1586880704932,
completed: null,
workerId: '/worker#ZbGaE-8YwQO-wT-JAAAA',
result: undefined,
error: undefined

sanitize git repository name (config.git.repository) in project-setup.js

4 cores cpu, having 8 worker nodes.
Steps to produce the issue:

1. trigger the build job 8 times, all going well. but when all job done, the JobWorker still show running in the web UI
2. once the 9th build job triggered, no worker node available. the job will pending for ever

Only way is to restart the SN-CICD server

The CICD process does not support "custom urls" - environment must be running under the "service-now.com" domain.

Replace hardcoded ".service-now.com" with ENV var as discussed here
#30 (comment)

The update sets deployed for Globally scoped applications is currently named as Global #. This results in update sets with duplicate names.
The deployed update set should be named as #

In case an update set contains XML records of another scope, these files are wrongly assigned to the update-set scope

like
https://github.com/vineeshnp/logram/blob/master/src/logram.js

An attempt was made to write more data to the response headers than there was room available in the buffer. Increase maxHttpHeaderSize on the connector or write less data into the response headers.: org.apache.coyote.http11.HeadersTooLargeException: An attempt was made to write more data to the response headers than there was room available in the buffer. Increase maxHttpHeaderSize on the connector or write less data into the response headers.: org.apache.coyote.http11.Http11OutputBuffer.checkLengthBeforeWrite(Http11OutputBuffer.java:544)
org.apache.coyote.http11.Http11OutputBuffer.write(Http11OutputBuffer.java:468)
org.apache.coyote.http11.Http11OutputBuffer.write(Http11OutputBuffer.java:454)
org.apache.coyote.http11.Http11OutputBuffer.sendHeader(Http11OutputBuffer.java:414)
org.apache.coyote.http11.Http11Processor.prepareResponse(Http11Processor.java:1388)
org.apache.coyote.AbstractProcessor.action(AbstractProcessor.java:373)
org.apache.coyote.Response.action(Response.java:208)
org.apache.coyote.Response.sendHeaders(Response.java:418)
org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:304)
org.apache.catalina.connector.OutputBuffer.flush(OutputBuffer.java:285)
org.apache.catalina.connector.CoyoteOutputStream.flush(CoyoteOutputStream.java:118)
com.glide.size_aware.SizeAwareServletOutputStream.flush(SizeAwareServletOutputStream.java:68)
java.util.zip.DeflaterOutputStream.flush(DeflaterOutputStream.java:282)
java.io.BufferedOutputStream.flush(BufferedOutputStream.java:141)
java.io.FilterOutputStream.flush(FilterOutputStream.java:140)
com.glide.rest.serializer.impl.ResponseSerializerImpl.closeOutputStream(ResponseSerializerImpl.java:166)
com.glide.rest.processors.RESTAPIProcessor.endRequestProcessing(RESTAPIProcessor.java:383)
com.glide.rest.processors.RESTAPIProcessor.endRequestProcessing(RESTAPIProcessor.java:372)
com.glide.rest.processors.RESTAPIProcessor.process(RESTAPIProcessor.java:301)
com.glide.processors.AProcessor.runProcessor(AProcessor.java:553)
com.glide.processors.AProcessor.processTransaction(AProcessor.java:240)
com.glide.processors.ProcessorRegistry.process0(ProcessorRegistry.java:177)
com.glide.processors.ProcessorRegistry.process(ProcessorRegistry.java:166)
com.glide.ui.GlideServletTransaction.process(GlideServletTransaction.java:31)
com.glide.sys.Transaction.run(Transaction.java:2192)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
java.lang.Thread.run(Thread.java:748)

Currently e-mail notifications works for failures (builds, deployments, preview, etc). Would it be possible to add e-mail notifications for the success criteria when build completes, pull request is open, pull request is merged, deployment in progress, and deployment complete?

The reason I am asking for this is because collaboration tools such as Slack is not available or allowed in the environment I currently work with and we would rather use e-mail notifications for now.

Please advise.

An Error is being encountered related to certificate validation at project setup - Error logs shown below:

[18:27:36.164] [ERROR] [2664] [/worker#Fh0RJQ1ejjKBQFxzAAAB] PROMISE JOB ERROR: Job 'projectSetup' { type: 'exe',
name: 'projectSetup',
options:
{ build: { requestor: [Object] },
atf: { updateSetOnly: false },
updateSet: '1db3fd101b41281494edddb6bc4bcb6a',
application:
{ id: 'bfb3a72c1b94641094edddb6bc4bcb2a',
name: 'MyCICDTestApp',
organization: 'company' },
git:
{ repository: 'x_g_nci_mycicdtest',
remoteUrl: null,
enabled: true,
pullRequestEnabled: true },
host: { name: 'https://service-sandbox.xxx.xxx/' } },
host: 'ncias-d2371-c',
id: 'bb5861f3-4db6-4fe8-b3b8-fd0dfb8df731',
emitter: { _events: {}, _eventsCount: 2 },
created: 1607470055957,
completed: null,
workerId: '/worker#Fh0RJQ1ejjKBQFxzAAAB',
result: undefined,
error: undefined } { Error: unable to verify the first certificate
at TLSSocket.onConnectSecure (_tls_wrap.js:1058:34)
at TLSSocket.emit (events.js:198:13)
at TLSSocket._finishInit (_tls_wrap.js:636:8) code: 'UNABLE_TO_VERIFY_LEAF_SIGNATURE' }
[18:27:36.217] [LOG] [5464] /worker#Fh0RJQ1ejjKBQFxzAAAB is done (/worker/done) with job: bb5861f3-4db6-4fe8-b3b8-fd0dfb8df731 Type: exe
[18:27:36.217] [ERROR] [5464] Job failed on worker { id: 'bb5861f3-4db6-4fe8-b3b8-fd0dfb8df731',
type: 'exe',
host: 'ncias-d2371-c',
platform: 'win32',
background: undefined } %j { name: 'RequestError',
message: 'Error: unable to verify the first certificate',
cause:
{ stack:
'Error: unable to verify the first certificate\n at TLSSocket.onConnectSecure (_tls_wrap.js:1058:34)\n at TLSSocket.emit (events.js:198:13)\n at TLSSocket._finishInit (_tls_wrap.js:636:8)',
message: 'unable to verify the first certificate',

I'm having an error in the Node app, when click in "Build this application button".
Config:

• CentOS 7
• Virtual Box VM
• 2GB RAM
• 30GB HD
• MID server running in the same server

Error:

Error text:
Unhandled rejection TypeError: Cannot read property 'match' of null
at CICD.module.exports (/home/vjbs/int-cicd/lib/modules/project-setup.js:471:36)
at Promise.try.then (/home/vjbs/int-cicd/lib/eb/run-module.js:75:34)
at tryCatcher (/home/vjbs/int-cicd/node_modules/bluebird/js/release/util.js:16:23)
at Promise._settlePromiseFromHandler (/home/vjbs/int-cicd/node_modules/bluebird/js/release/promise.js:517:31)
at Promise._settlePromise (/home/vjbs/int-cicd/node_modules/bluebird/js/release/promise.js:574:18)
at Promise._settlePromiseCtx (/home/vjbs/int-cicd/node_modules/bluebird/js/release/promise.js:611:10)
at _drainQueueStep (/home/vjbs/int-cicd/node_modules/bluebird/js/release/async.js:142:12)
at _drainQueue (/home/vjbs/int-cicd/node_modules/bluebird/js/release/async.js:131:9)
at Async._drainQueues (/home/vjbs/int-cicd/node_modules/bluebird/js/release/async.js:147:5)
at Immediate.Async.drainQueues [as _onImmediate] (/home/vjbs/int-cicd/node_modules/bluebird/js/release/async.js:17:14)
at runCallback (timers.js:705:18)
at tryOnImmediate (timers.js:676:5)
at processImmediate (timers.js:658:5)

a new feature may need to encrypt the password in side .env config, for some security policy reasons config file can't keep clear password.

Originally posted by @gitlabbin in #5 (comment)

When the deployment from CICD fails in target environment, customer updates are missing. The US is streamed from GIT.

In CICD Integration > Properties for the "The CICD Server Hostname" Property, it would save time to test to see if the connection is good before having to finish the set up and run a test CICD pipeline to see if the connection is good or not. This could also be used in MID server to be used.

When we migrate updateset from dev instance to test instance,
some updateset requires additional data or configuration changes.

• Configure system properties or other instance-specific settings
• group or role

How will SN-CICD handle it? or any good practice for that case?

some developers seem to manage to change the scope of an update set.
The system must discover app change and cleanup dependent old run, build, etc records

I'm trying to implement sn-cicd in New York taking the example but I'm currently stuck in the place where I need to build the test application which i uploaded.
The UI action thats supposed to run the build isnt displayed in New York release.
Any heads up ?

When using git as the source for update set, update set is being loaded in target environment, but commit fails because of scope errors. This happens both for scoped and global applications.
Cannot commit Update Set 'Default' because: Update scope id '03852e7f4f613300a3cc121f9310c728' is different than update set scope id 'x_317910_latest28'. Resolve the problem before committing.
Same update set works if i disable deployment from git.
Not sure it is related but i see below error in Logs:-
GetKeys failed (com.glide.processors.soap.SOAPProcessingException: Web service not found: api/devops/cicd/source/sys_scope com.glide.processors.soap.SOAPProcessingException: Web service not found: api/devops/cicd/source/sys_scope

https://www.npmjs.com/package/dotenv-safe

Identical to dotenv, but ensures that all necessary environment variables are defined after reading from .env. These needed variables are read from .env.example, which should be commited along with your project.

Scenario

Deploy commit-3 to Target; As expected, commit-2 is not deployed since commit-3 is a FIX deployment

Now deploy commit-5 to Target,
Finding: commit-2 is still not deployed to Target
Cause: baselineCommitId should ideally be commit-1 and not commit-3