• Type: Task
• Resolution: Fixed
• Priority: Critical
• Component/s: blueocean-plugin
• Labels:

  • technical-debt

[JENKINS-43906] Creation tests for "Git" flow

Cliff Meyers created issue - 2017-04-27 14:13

Cliff Meyers made changes - 2017-04-27 14:13

Epic Link

New: JENKINS-36178 [ 172150 ]

Cliff Meyers made changes - 2017-04-27 14:13

Description

Original: Covering Git (with credentials) and github is required to make the ATH coverage complete.  Requirements [https://docs.google.com/document/d/1LrVg65dHs89RJ-IFDrlgQjGYPAQCgysO4YXa7TxzAXE/edit]   In scope:   * Creating a pipeline via git with existing Jenkinsfile  * Opening editor on existing declarative Jenkinsfile in github  * Creating a pipeline based on "empty" repo, that opens an editor from github, create a new stage/step and save a new pipeline   (can split this up if it seems to bit - as git alone may be starting point..)

New: Covering Git (with credentials) is required to make the ATH coverage complete.  Requirements [https://docs.google.com/document/d/1LrVg65dHs89RJ-IFDrlgQjGYPAQCgysO4YXa7TxzAXE/edit]   In scope:   * Creating a pipeline via git with existing Jenkinsfile

Cliff Meyers made changes - 2017-04-27 14:15

Link

New: This issue is related to JENKINS-42600 [ JENKINS-42600 ]

Cliff Meyers made changes - 2017-04-27 14:46

Description

Original: Covering Git (with credentials) is required to make the ATH coverage complete.  Requirements [https://docs.google.com/document/d/1LrVg65dHs89RJ-IFDrlgQjGYPAQCgysO4YXa7TxzAXE/edit]   In scope:   * Creating a pipeline via git with existing Jenkinsfile

New: Covering Git (with credentials) is required to make the ATH coverage complete.  Requirements [https://docs.google.com/document/d/1LrVg65dHs89RJ-IFDrlgQjGYPAQCgysO4YXa7TxzAXE/edit] In scope:   * Creating a pipeline via git with existing Jenkinsfile || SCM || Repo Type || Clone URL || Credentials? || Jenkinsfile? || Success? || Activity || Notes || | BitBucket | Public | HTTPS | "Default" | Yes | Success | 2 Builds | https://bitbucket.org/cliffmeyers/jenkins-test-public-1 | BitBucket | Public | HTTPS | "Default" | Yes | Success | "No Jenkinsfile" | https://bitbucket.org/cliffmeyers/jenkins-test-public-empty |

Cliff Meyers made changes - 2017-04-27 14:55

Description

Original: Covering Git (with credentials) is required to make the ATH coverage complete.  Requirements [https://docs.google.com/document/d/1LrVg65dHs89RJ-IFDrlgQjGYPAQCgysO4YXa7TxzAXE/edit] In scope:   * Creating a pipeline via git with existing Jenkinsfile || SCM || Repo Type || Clone URL || Credentials? || Jenkinsfile? || Success? || Activity || Notes || | BitBucket | Public | HTTPS | "Default" | Yes | Success | 2 Builds | https://bitbucket.org/cliffmeyers/jenkins-test-public-1 | BitBucket | Public | HTTPS | "Default" | Yes | Success | "No Jenkinsfile" | https://bitbucket.org/cliffmeyers/jenkins-test-public-empty |

New: Covering Git (with credentials) is required to make the ATH coverage complete.  Requirements [https://docs.google.com/document/d/1LrVg65dHs89RJ-IFDrlgQjGYPAQCgysO4YXa7TxzAXE/edit] In scope:   * Creating a pipeline via git with existing Jenkinsfile || SCM || Repo Type || Clone URL || Credentials? || Jenkinsfile? || Success? || Details || | BitBucket | Public | HTTPS | "Default" | Yes | Yes | Activity w/ builds | | BitBucket | Public | HTTPS | "Default" | No | Yes | Activity "No Jenkinsfile" | | BitBucket | Private | HTTPS | "Default" | Yes | No | "Invalid Credential" | | BitBucket | Private | HTTPS | Invalid Cred | Yes | No | "Invalid Credential" | | BitBucket | Private | HTTPS | Valid | Yes | Yes | Activity w/ builds | | BitBucket | Public | SSH | "Default" | Yes | Yes | Public repos don't seem to work unless the key is actually tied to the owning account? Need to confirm this and update these scenarios. | | BitBucket | Private | SSH | Any username / password | Yes | "Invalid Credential" | | | BitBucket | Private | SSH | Any username / password | Yes | "Invalid Credential" | |

Cliff Meyers made changes - 2017-04-27 14:59

Description

Original: Covering Git (with credentials) is required to make the ATH coverage complete.  Requirements [https://docs.google.com/document/d/1LrVg65dHs89RJ-IFDrlgQjGYPAQCgysO4YXa7TxzAXE/edit] In scope:   * Creating a pipeline via git with existing Jenkinsfile || SCM || Repo Type || Clone URL || Credentials? || Jenkinsfile? || Success? || Details || | BitBucket | Public | HTTPS | "Default" | Yes | Yes | Activity w/ builds | | BitBucket | Public | HTTPS | "Default" | No | Yes | Activity "No Jenkinsfile" | | BitBucket | Private | HTTPS | "Default" | Yes | No | "Invalid Credential" | | BitBucket | Private | HTTPS | Invalid Cred | Yes | No | "Invalid Credential" | | BitBucket | Private | HTTPS | Valid | Yes | Yes | Activity w/ builds | | BitBucket | Public | SSH | "Default" | Yes | Yes | Public repos don't seem to work unless the key is actually tied to the owning account? Need to confirm this and update these scenarios. | | BitBucket | Private | SSH | Any username / password | Yes | "Invalid Credential" | | | BitBucket | Private | SSH | Any username / password | Yes | "Invalid Credential" | |

New: Covering Git (with credentials) is required to make the ATH coverage complete.  Requirements [https://docs.google.com/document/d/1LrVg65dHs89RJ-IFDrlgQjGYPAQCgysO4YXa7TxzAXE/edit] Scope Ideally we'd test all of the below scenarios:   ||SCM||Repo Type||Clone URL||Credentials?||Jenkinsfile?||Success?||Details|| |BitBucket|Public|HTTPS|"Default"|Yes|Yes|Activity w/ builds| |BitBucket|Public|HTTPS|"Default"|No|Yes|Activity "No Jenkinsfile"| |BitBucket|Private|HTTPS|"Default"|Yes|No|"Invalid Credential"| |BitBucket|Private|HTTPS|Invalid user / pass|Yes|No|"Invalid Credential"| |BitBucket|Private|HTTPS|Valid user / pass|Yes|Yes| | |BitBucket|Public|SSH|"Default"|Yes|Yes|Public repos don't seem to work unless the key is actually tied to the owning account? Need to confirm this and update these scenarios.| |BitBucket|Private|SSH|Invalid private key|Yes|No|"Invalid Credential"| |BitBucket|Private|SSH|Valid private key|Yes|Yes| |

Cliff Meyers made changes - 2017-04-27 15:00

Description

Original: Covering Git (with credentials) is required to make the ATH coverage complete.  Requirements [https://docs.google.com/document/d/1LrVg65dHs89RJ-IFDrlgQjGYPAQCgysO4YXa7TxzAXE/edit] Scope Ideally we'd test all of the below scenarios:   ||SCM||Repo Type||Clone URL||Credentials?||Jenkinsfile?||Success?||Details|| |BitBucket|Public|HTTPS|"Default"|Yes|Yes|Activity w/ builds| |BitBucket|Public|HTTPS|"Default"|No|Yes|Activity "No Jenkinsfile"| |BitBucket|Private|HTTPS|"Default"|Yes|No|"Invalid Credential"| |BitBucket|Private|HTTPS|Invalid user / pass|Yes|No|"Invalid Credential"| |BitBucket|Private|HTTPS|Valid user / pass|Yes|Yes| | |BitBucket|Public|SSH|"Default"|Yes|Yes|Public repos don't seem to work unless the key is actually tied to the owning account? Need to confirm this and update these scenarios.| |BitBucket|Private|SSH|Invalid private key|Yes|No|"Invalid Credential"| |BitBucket|Private|SSH|Valid private key|Yes|Yes| |

New: Covering Git (with credentials) is required to make the ATH coverage complete.  Requirements [https://docs.google.com/document/d/1LrVg65dHs89RJ-IFDrlgQjGYPAQCgysO4YXa7TxzAXE/edit] Scope Ideally we'd test all of the below scenarios:   ||SCM||Repo Type||Clone URL||Credentials?||Jenkinsfile?||Success?||Details|| |BitBucket|Public|HTTPS|"Default"|Yes|Yes|Activity w/ builds| |BitBucket|Public|HTTPS|"Default"|No|Yes|Activity "No Jenkinsfile"| |BitBucket|Private|HTTPS|"Default"|Yes|No|"Invalid Credential"| |BitBucket|Private|HTTPS|Invalid user / pass|Yes|No|"Invalid Credential"| |BitBucket|Private|HTTPS|Valid user / pass|Yes|Yes| | |BitBucket|Public|SSH|"Default"|Yes|No?|I believe SSH always requires a valid key whether it's public or private? Needs confirming.| |BitBucket|Private|SSH|Invalid private key|Yes|No|"Invalid Credential"| |BitBucket|Private|SSH|Valid private key|Yes|Yes| |

Cliff Meyers made changes - 2017-04-28 13:21

Description

Original: Covering Git (with credentials) is required to make the ATH coverage complete.  Requirements [https://docs.google.com/document/d/1LrVg65dHs89RJ-IFDrlgQjGYPAQCgysO4YXa7TxzAXE/edit] Scope Ideally we'd test all of the below scenarios:   ||SCM||Repo Type||Clone URL||Credentials?||Jenkinsfile?||Success?||Details|| |BitBucket|Public|HTTPS|"Default"|Yes|Yes|Activity w/ builds| |BitBucket|Public|HTTPS|"Default"|No|Yes|Activity "No Jenkinsfile"| |BitBucket|Private|HTTPS|"Default"|Yes|No|"Invalid Credential"| |BitBucket|Private|HTTPS|Invalid user / pass|Yes|No|"Invalid Credential"| |BitBucket|Private|HTTPS|Valid user / pass|Yes|Yes| | |BitBucket|Public|SSH|"Default"|Yes|No?|I believe SSH always requires a valid key whether it's public or private? Needs confirming.| |BitBucket|Private|SSH|Invalid private key|Yes|No|"Invalid Credential"| |BitBucket|Private|SSH|Valid private key|Yes|Yes| |

New: Covering Git (with credentials) is required to make the ATH coverage complete.  Requirements [https://docs.google.com/document/d/1LrVg65dHs89RJ-IFDrlgQjGYPAQCgysO4YXa7TxzAXE/edit] Scope Ideally we'd test all of the below scenarios:   ||Priority||SCM||Repo Type||Clone URL||Credentials?||Jenkinsfile?||Success?||Details|| | 1 |BitBucket|Public|HTTPS|"Default"|Yes|Yes|Activity w/ builds| | 1 |BitBucket|Public|HTTPS|"Default"|No|Yes|Activity "No Jenkinsfile"| | 4 |BitBucket|Private|HTTPS|"Default"|Yes|No|"Invalid Credential"| | 3 |BitBucket|Private|HTTPS|Invalid user / pass|Yes|No|"Invalid Credential"| | 2 |BitBucket|Private|HTTPS|Valid user / pass|Yes|Yes| | | 4 |BitBucket|Public|SSH|"Default"|Yes|No?|I believe SSH always requires a valid key whether it's public or private? Needs confirming.| | 3 |BitBucket|Private|SSH|Invalid private key|Yes|No|"Invalid Credential"| | 2 |BitBucket|Private|SSH|Valid private key|Yes|Yes| |

Cliff Meyers made changes - 2017-04-28 13:21

Description

Original: Covering Git (with credentials) is required to make the ATH coverage complete.  Requirements [https://docs.google.com/document/d/1LrVg65dHs89RJ-IFDrlgQjGYPAQCgysO4YXa7TxzAXE/edit] Scope Ideally we'd test all of the below scenarios:   ||Priority||SCM||Repo Type||Clone URL||Credentials?||Jenkinsfile?||Success?||Details|| | 1 |BitBucket|Public|HTTPS|"Default"|Yes|Yes|Activity w/ builds| | 1 |BitBucket|Public|HTTPS|"Default"|No|Yes|Activity "No Jenkinsfile"| | 4 |BitBucket|Private|HTTPS|"Default"|Yes|No|"Invalid Credential"| | 3 |BitBucket|Private|HTTPS|Invalid user / pass|Yes|No|"Invalid Credential"| | 2 |BitBucket|Private|HTTPS|Valid user / pass|Yes|Yes| | | 4 |BitBucket|Public|SSH|"Default"|Yes|No?|I believe SSH always requires a valid key whether it's public or private? Needs confirming.| | 3 |BitBucket|Private|SSH|Invalid private key|Yes|No|"Invalid Credential"| | 2 |BitBucket|Private|SSH|Valid private key|Yes|Yes| |

New: Covering Git (with credentials) is required to make the ATH coverage complete.  Requirements [https://docs.google.com/document/d/1LrVg65dHs89RJ-IFDrlgQjGYPAQCgysO4YXa7TxzAXE/edit] Scope Ideally we'd test all of the below scenarios:   ||Priority||SCM||Repo Type||Clone URL||Credentials?||Jenkinsfile?||Success?||Details|| | 1 |BitBucket|Public|HTTPS|"Default"|Yes|Yes|Activity w/ builds| | 1 |BitBucket|Public|HTTPS|"Default"|No|Yes|Activity "No Jenkinsfile"| | 4 |BitBucket|Private|HTTPS|"Default"|Yes|No|"Invalid Credential"| | 3 |BitBucket|Private|HTTPS|Invalid user / pass|Yes|No|"Invalid Credential"| | 2 |BitBucket|Private|HTTPS|Valid user / pass|Yes|Yes| | | 4 |BitBucket|Public|SSH|"Default"|Yes|No?|I believe SSH always requires a valid key whether it's public or private?| | 3 |BitBucket|Private|SSH|Invalid private key|Yes|No|"Invalid Credential"| | 2 |BitBucket|Private|SSH|Valid private key|Yes|Yes| |

Michael Neale made changes - 2017-06-02 01:50

Sprint

New: Blue Ocean 1.2 [ 326 ]

Michael Neale made changes - 2017-06-02 01:50

Rank

New: Ranked higher

Load more newer history items