1. 25 12月, 2017 2 次提交
  2. 20 12月, 2017 2 次提交
  3. 18 12月, 2017 2 次提交
  4. 16 12月, 2017 1 次提交
    • W
      [JENKINS-22474] API Token does not require CSRF token (#3129) · 814d2027
      Wadeck Follonier 提交于
      * [JENKINS-22474] API Token does not require CSRF token
      - in order to ease the use of the api, we are not requiring the request to have a crumb
      - in terms of security it's not a problem normally since the CSRF attacks use the cookies and in case of API Token, it's session-less / cookie-less
      
      * - adjust the license header
      
      * - add test for basic authentication
      - add test for login process
      
      * - add test for form submission using ui (htmlunit), not just login form
      
      * - modification requested by Jesse
      
      * - pom.xml update to use the last version of jenkins-test-harness (with the token helper methods)
      - beginning of the simplification of tests
      
      * - using the try-with-resource approach to ease readability
      
      * - using closure method now
      
      * - add missing login transformation
      
      * - add unit test
      
      * - use withToken
      - remove useless crumb for GET method
      - add fail (otherwise the assert in catch is not as useful as it could be)
      
      * another bunch of test cases
      
      * - for HudsonTestCase, some additional modifications are required: changing the view / different type of management for the variable inside the views
      
      * - small other tests
      
      * - last batch for the login method
      
      * - crumb is not more required since we are using API Token
      
      * - converting auth to ApiToken to avoid crumb method
      
      * - converting auth to ApiToken to avoid crumb method (second)
      
      * - remove usage of closure aware methods
      
      * - update the pom using the snapshot as adviced by Jesse
      - modifications on other class to adapt to the last modifications in JTH
      
      * - modifications requested during code review
      
      * - also put back my changes to the conflicted file
      
      * - correction of the merge :)
      814d2027
  5. 14 12月, 2017 2 次提交
  6. 12 12月, 2017 2 次提交
  7. 09 12月, 2017 4 次提交
  8. 08 12月, 2017 2 次提交
  9. 07 12月, 2017 2 次提交
  10. 04 12月, 2017 2 次提交
  11. 27 11月, 2017 2 次提交
  12. 23 11月, 2017 2 次提交
    • B
      Fix RequireUpperBoundDeps issue · fed7f2e3
      Baptiste Mathus 提交于
      ```
      WARNING] Rule 3: org.apache.maven.plugins.enforcer.RequireUpperBoundDeps fai
      Failed while enforcing RequireUpperBoundDeps. The error(s) are [
      Require upper bound dependencies error for org.objenesis:objenesis:2.1 paths
      +-org.jenkins-ci.main:test:2.92-SNAPSHOT
        +-org.mockito:mockito-core:1.10.19
          +-org.objenesis:objenesis:2.1
      and
      +-org.jenkins-ci.main:test:2.92-SNAPSHOT
        +-org.awaitility:awaitility:3.0.0
          +-org.objenesis:objenesis:2.5.1
      ```
      fed7f2e3
    • B
      Retry assertion for 10 seconds before failing · e50d4d71
      Baptiste Mathus 提交于
      Also reduce the time 250 ms (instead of 1 second previously) between
      retries to hopefully reduce the test duration on quick enough setups,
      and still degrade nicely on less performing ones.
      e50d4d71
  13. 20 11月, 2017 2 次提交
  14. 13 11月, 2017 2 次提交
  15. 10 11月, 2017 1 次提交
  16. 07 11月, 2017 4 次提交
  17. 06 11月, 2017 2 次提交
  18. 30 10月, 2017 2 次提交
  19. 23 10月, 2017 2 次提交