🔥 removed api token validation

maykinmedia · May 3, 2024 · ea9eeb4 · ea9eeb4
1 parent 7f60637
commit ea9eeb4
Show file tree

Hide file tree

Showing 35 changed files with 133 additions and 748 deletions.
diff --git a/Jenkinsfile b/Jenkinsfile
diff --git a/README.rst b/README.rst
@@ -34,9 +34,9 @@ References
 * `Code <https://bitbucket.org/maykinmedia/referentielijsten>`_
 
 
-.. |build-status| image:: http://jenkins.maykin.nl/buildStatus/icon?job=bitbucket/referentielijsten/master
+.. |build-status| image:: https://github.com/maykinmedia/referentielijsten/workflows/ci/badge.svg?branch=master
     :alt: Build status
-    :target: http://jenkins.maykin.nl/job/referentielijsten
+    :target: https://github.com/maykinmedia/referentielijsten/actions?query=workflow%3Aci
 
 .. |requirements| image:: https://requires.io/bitbucket/maykinmedia/referentielijsten/requirements.svg?branch=master
      :target: https://requires.io/bitbucket/maykinmedia/referentielijsten/requirements/?branch=master

diff --git a/bootstrap.py b/bootstrap.py
@@ -18,8 +18,8 @@
 parser = argparse.ArgumentParser(description=description)
 parser.add_argument(
     "target",
-    choices=["production", "staging", "test", "jenkins", "dev"],
-    help="production/staging/test/jenkins/dev",
+    choices=["production", "staging", "test", "ci", "dev"],
+    help="production/staging/test/ci/dev",
 )
 parser.add_argument(
     "--project",

diff --git a/ci/Dockerfile b/ci/Dockerfile
diff --git a/ci/jenkins.sh b/ci/jenkins.sh
diff --git a/ci/myproject/.gitkeep b/ci/myproject/.gitkeep
diff --git a/ci/run_ci.sh b/ci/run_ci.sh
diff --git a/docs/testing.rst b/docs/testing.rst
@@ -28,24 +28,6 @@ and::
     $ alias cov_runtests='coverage run src/manage.py test --keepdb'
     $ cov_runtests src && chromium htmlcov/index.html
 
-
-Jenkins
--------
-
-Run ``./bin/jenkins_django.sh`` to execute the tests for ``develop`` and ``master``.
-This script runs the tests with ``--keepdb``.
-
-To run PR tests, run ``./bin/jenkins_django_pr.sh``. This script drops the test
-database at the end, so it should be safe with different migrations between PR's.
-
-
-SASS build - Jenkins
-====================
-
-There is a simple ``./bin/jenkins_sass.sh`` script that checks if the sass
-compiles successfully.
-
-
 Javascript tests
 ================
 
@@ -69,37 +51,3 @@ To trigger a test run on file change (source file or test file), run::
 
     $ karma start karma.conf.js --single-run=false --browsers=PhantomJS
 
-
-Jenkins
--------
-
-On Jenkins, the tests are run against PhantomJS and Chrome. Therefore, ``xfvb``
-needs to be available.
-
-Run the tests by invoking ``./bin/jenkins_js.sh``.
-
-
-Jenkins jobs
-============
-
-It is recommended to set up the following Jenkins jobs for a project:
-
-**master** branch
------------------
-
-1. ``referentielijsten-django``: backend tests, runs ``./bin/jenkins_django.sh``.
-2. ``referentielijsten-js``: frontend tests, runs ``./bin/jenkins_js.sh``.
-
-**develop** branch
-------------------
-
-1. ``referentielijsten-django-develop``: backend tests, runs ``./bin/jenkins_django.sh``.
-2. ``referentielijsten-django-develop-js``: frontend tests, runs ``./bin/jenkins_js.sh``.
-
-pull requests
--------------
-1. ``referentielijsten-pr-django``: backend tests, runs ``./bin/jenkins_django_pr.sh``.
-2. ``referentielijsten-pr-js``: frontend tests, runs ``./bin/jenkins_js.sh``.
-3. ``referentielijsten-pr-sass``: checks that sass compiles, runs ``./bin/jenkins_sass.sh``.
-4. ``referentielijsten-pr-isort``: checks that imports are correctly
-   sorted, runs ``./bin/jenkins_isort.sh``.
diff --git a/setup.cfg b/setup.cfg
@@ -16,7 +16,7 @@ ensure_newline_before_comments = True
 skip = env,node_modules
 skip_glob = **/migrations/**
 known_django=django
-known_first_party=openklant
+known_first_party=referentielijsten
 sections=FUTURE,STDLIB,DJANGO,THIRDPARTY,FIRSTPARTY,LOCALFOLDER
 
 ; black compatible settings