[BUILD-1159] keep Selenium in sync for multiple projects Created: 19/Oct/23 Updated: 15/Nov/23 Resolved: 15/Nov/23 |
|
| Status: | Closed |
| Project: | Build |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Christoph Meier | Assignee: | Harshini Pola |
| Resolution: | Resolved | Votes: | 0 |
| Labels: | TAE | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Template: |
|
||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||
| Task DoR: |
Empty
|
||||||||||||||||
| Date of First Response: | |||||||||||||||||
| Epic Link: | TAE-build-or-infra-tasks | ||||||||||||||||
| Team: | |||||||||||||||||
| Work Started: | |||||||||||||||||
| Approved: |
Yes
|
||||||||||||||||
| Description |
Context Approach In the Jenkins pipeline- we need to download the script and create "dynamically" the .env before calling docker-compose. What about running tests locally? The above mentioned approach should work fine on Jenkins. To workaround this - each project could still contain a .env file with a literal value for the SELENIUM_VERSION. On jenkins we would just override the file. |
| Comments |
| Comment by Christoph Meier [ 23/Oct/23 ] |
|
Consider to check for inspiration ... as related tickets |
| Comment by Christoph Meier [ 06/Nov/23 ] |
|
SRE.JENKINS Done:
pending approval ??
nearly done:
CORE.JENKINS
|
| Comment by Harshini Pola [ 08/Nov/23 ] |
|
SRE.JENKINS
CORE.JENKINS |
| Comment by Harshini Pola [ 15/Nov/23 ] |
|
Updated in all SRE.Jenkins projects., reviewed and merged. |