You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
--Needed for testing coverage outside of main UT3 schema.
73
-
grant create any procedure, drop any procedure, execute any procedure, create any type, drop any type, execute any type, under any type, select any table, update any table, insert any table, delete any table, create any table, drop any table, alter any table, select any dictionary to $UT3_TESTER;
74
-
revoke execute on dbms_crypto from $UT3_TESTER;
75
-
grant create job to $UT3_TESTER;
73
+
--needed for disabling DDL trigger and testint parser without trigger enabled/present
74
+
grant alter any trigger to ut3_tester;
75
+
grant administer database trigger to $UT3_TESTER;
76
76
exit
77
77
SQL
78
78
79
-
#Create additional UT3$USER# to test for special characters
79
+
#Create additional UT3$USER# to test for special characters and front end API testing
80
80
time"$SQLCLI" sys/$ORACLE_PWD@//$CONNECTION_STR AS SYSDBA <<-SQL
grant create public database link to $UT3_TESTER_HELPER;
94
+
grant drop public database link to $UT3_TESTER_HELPER;
95
+
set feedback on
96
+
--Needed for testing coverage outside of main UT3 schema.
97
+
grant create any procedure, drop any procedure, execute any procedure, create any type, drop any type, execute any type, under any type, select any table, update any table, insert any table, delete any table, create any table, drop any table, alter any table, select any dictionary, create any synonym, drop any synonym to $UT3_TESTER_HELPER;
98
+
grant create job to $UT3_TESTER_HELPER;
99
+
--Needed to allow for enable/disable of annotation triggers
100
+
grant administer database trigger to $UT3_TESTER_HELPER;
Copy file name to clipboardExpand all lines: development/cleanup.sh
+3-2Lines changed: 3 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -21,16 +21,17 @@ end;
21
21
drop user ${UT3_OWNER} cascade;
22
22
drop user ${UT3_RELEASE_VERSION_SCHEMA} cascade;
23
23
drop user ${UT3_TESTER} cascade;
24
+
drop user ${UT3_TESTER_HELPER} cascade;
24
25
drop user ${UT3_USER} cascade;
25
26
26
27
begin
27
28
for i in (
28
-
select decode(owner,'PUBLIC','drop public synonym "','drop synonym "'||owner||'"."')|| synonym_name ||'"' drop_orphaned_synonym from dba_synonyms a
29
+
select decode(owner,'PUBLIC','drop public synonym "','drop synonym "'||owner||'"."')|| synonym_name ||'"' drop_orphaned_synonym, owner||'.'||synonym_name syn from dba_synonyms a
29
30
where not exists (select 1 from dba_objects b where (a.table_name=b.object_name and a.table_owner=b.owner or b.owner='SYS' and a.table_owner=b.object_name) )
Copy file name to clipboardExpand all lines: development/releasing.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,18 +7,20 @@ To create a release:
7
7
- create release branch from development branch and make sure to name the release branch: `release/vX.Y.Z`
8
8
- update, commit and push at least one file change in the release branch, to kickoff a Travis build
9
9
- wait for th build to complete successfully
10
-
- merge the release branch to master and wait for master build to complete successfully
11
-
- create a release from the master branch using [github releases page](https://github.com/utPLSQL/utPLSQL/releases) and populate release description using information found on the issues and pull requests since previous release.
10
+
- merge the release branch to master and wait for master build to complete successfully (do not use Squash/rebase for merge operation)
11
+
- create a Github release from the master branch using [github releases page](https://github.com/utPLSQL/utPLSQL/releases) and populate release description using information found on the issues and pull requests since previous release.
12
12
To find issues closed after certain date use [advanced filters](https://help.github.com/articles/searching-issues-and-pull-requests/#search-by-open-or-closed-state).
- After release was successfully built, merge master branch back into develop branch
14
+
- After A build was completed on a TAG (github release) was successful, merge master branch back into develop branch.
15
+
- At this point, master branch and release tag should be at the same commit version and artifacts should be uploaded into Github release.
15
16
- After develop branch was built, update version number in `VERSION` file to represent next planned release version.
16
17
- Clone `utplsql.githug.io` project and add a new announcement about next version being released in `_posts`. Use previous announcements as a template. Make sure to set date, time and post title properly.
17
18
18
19
The following will happen:
19
20
- build executed on branch `release/vX.Y.Z-[something]` updates files `sonar-project.properties`, `VERSION` with project version derived from the release branch name
20
21
- changes to those two files are committed and pushed back to release branch by Travis
21
-
- when a release is created, a new tag is added in on the repository and a tag build is executed
22
+
- builds on master branch are **not getting executed**
23
+
- when a Github release is created, a new tag is added in on the repository and a tag build is executed
22
24
- the documentation for new release is published on `utplsql.github.io` and installation archives are added to the tag.
0 commit comments