add manifest/3.2.xml back to product-config.json as a disabled entry. #6760
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Describe your PR here...
currently, build-from-manifest-new keeps triggering manifest/3.2.xml and manifest/default.xml. Since both are 3.2.0, it causes https://github.com/couchbase/build-manifests/blob/master/sync_gateway/3.2.0/3.2.0.xml to be different on every scan. This results in a new build on every single scan. Having a disabled manifest/3.2.xml entry should stop "manifest/3.2.xml" from getting triggered.
-Ming
Pre-review checklist
fmt.Print
,log.Print
, ...)base.UD(docID)
,base.MD(dbName)
)docs/api
Dependencies (if applicable)
Integration Tests
GSI=true,xattrs=true
https://jenkins.sgwdev.com/job/SyncGateway-Integration/000/