If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 08/May/18 06:12 PM
Updated: 28/Feb/19 03:10 PM
|
|
Component/s: |
None
|
Affects Version/s: |
8.0.4
|
Fix Version/s: |
None
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
Environment:
|
Operating System: Windows 10 Enterprise 64-bit (10.0, Build 16299) (16299.rs3_release.170928-1534)
Memory: 65536MB RAM
java.runtime.version 1.8.0_162-b12
Operating System: Windows 10 Enterprise 64-bit (10.0, Build 16299) (16299.rs3_release.170928-1534)
Memory: 65536MB RAM
java.runtime.version 1.8.0_162-b12
|
|
impact: User Confusion
Experienced: On a new, default install of qb8.0, I created a build and put it on a Periodical schedule. The build never triggered because it never satisfied the default build condition of "If changes found in referenced repositories: Include/Exclude Path Patterns: not defined."
Expected: The default, new install, out of the box build condition should be "Always build." New users that have never used Quickbuild on a new install wouldn't know what was happening and why it wasn't triggering. I thought this was a bug in schedules for QB 8.0 until I asked my senior engineer, Raul.
Repro:
1. Download a new install of QB 8.0.4
2. Extract QB and run server.bat/sh start
3. Navigate to root after initial install
4. Click on General Settings
5. Observe the Default build condition
6. Create a new configuration
7. Put the build on a schedule and observe it never triggers.
|
Description
|
impact: User Confusion
Experienced: On a new, default install of qb8.0, I created a build and put it on a Periodical schedule. The build never triggered because it never satisfied the default build condition of "If changes found in referenced repositories: Include/Exclude Path Patterns: not defined."
Expected: The default, new install, out of the box build condition should be "Always build." New users that have never used Quickbuild on a new install wouldn't know what was happening and why it wasn't triggering. I thought this was a bug in schedules for QB 8.0 until I asked my senior engineer, Raul.
Repro:
1. Download a new install of QB 8.0.4
2. Extract QB and run server.bat/sh start
3. Navigate to root after initial install
4. Click on General Settings
5. Observe the Default build condition
6. Create a new configuration
7. Put the build on a schedule and observe it never triggers.
|
Show » |
There are no comments yet on this issue.
|
|